How severe is GHSA-wrw9-m778-g6mc?

No CVSS score has been assigned to GHSA-wrw9-m778-g6mc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wrw9-m778-g6mc?

GHSA-wrw9-m778-g6mc affects the following packages: bl (npm), bl (npm). Ecosystems affected: npm.

How do I fix GHSA-wrw9-m778-g6mc?

Update bl to 0.9.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wrw9-m778-g6mc is resolved across your whole dependency graph.

How do I detect GHSA-wrw9-m778-g6mc in my npm dependencies?

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.

How do I mitigate GHSA-wrw9-m778-g6mc if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-wrw9-m778-g6mc?

O3 pinpoints whether GHSA-wrw9-m778-g6mc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-wrw9-m778-g6mc actively exploited in the wild?

No public exploit code has been indexed for GHSA-wrw9-m778-g6mc yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-wrw9-m778-g6mc published, and has it been updated?

GHSA-wrw9-m778-g6mc was published on June 3, 2019 and was last updated on August 31, 2020. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-wrw9-m778-g6mc

Fix: rvagg/bl#22

GHSA-wrw9-m778-g6mc is a security vulnerability in bl. O3 Security confirms whether GHSA-wrw9-m778-g6mc is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Memory Exposure in bl

Published

Jun 3, 2019

Updated

Aug 31, 2020

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

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.

2Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

blnpm

82.8Mdownloads / week

Description

Versions of bl before 0.9.5 and 1.0.1 are vulnerable to memory exposure.

bl.append(number) in the affected bl versions passes a number to Buffer constructor, appending a chunk of uninitialized memory

Recommendation

Update to version 0.9.5, 1.0.1 or later.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`bl`	all versions	0.9.5
📦npm	`bl`	≥ 1.0.0&&< 1.0.1	1.0.1

Detection & mitigation playbook

Open-source dependency

Detect
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 0.9.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wrw9-m778-g6mc 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-wrw9-m778-g6mc 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-wrw9-m778-g6mc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of `bl` before 0.9.5 and 1.0.1 are vulnerable to memory exposure. `bl.append(number)` in the affected `bl` versions passes a number to Buffer constructor, appending a chunk of uninitialized memory ## Recommendation Update to version 0.9.5, 1.0.1 or later.

O3 Security · Impact-Aware SCA

Is GHSA-wrw9-m778-g6mc in your dependencies?

O3 detects GHSA-wrw9-m778-g6mc across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works