GHSA-pp7h-53gx-mx7r is a medium-severity (CVSS 6.5) CWE-126 vulnerability in bl. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-pp7h-53gx-mx7r is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Remote Memory Exposure in bl
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
blnpmDescription
A buffer over-read vulnerability exists in bl <4.0.3, <3.0.1, <2.2.1, and <1.2.3 which could allow an attacker to supply user input (even typed) that if it ends up in consume() argument and can become negative, the BufferList state can be corrupted, tricking it into exposing uninitialized memory via regular .slice() calls.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | bl | all versions | 1.2.3 |
| 📦npm | bl | ≥ 2.0.0&&< 2.2.1 | 2.2.1 |
| 📦npm | bl | ≥ 3.0.0&&< 3.0.1 | 3.0.1 |
| 📦npm | bl | ≥ 4.0.0&&< 4.0.3 | 4.0.3 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bl. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update bl to 1.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pp7h-53gx-mx7r is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-pp7h-53gx-mx7r is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-pp7h-53gx-mx7r. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-pp7h-53gx-mx7r in your dependencies?
O3 detects GHSA-pp7h-53gx-mx7r across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.