How severe is GHSA-jgqf-hwc5-hh37?

GHSA-jgqf-hwc5-hh37 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-jgqf-hwc5-hh37?

GHSA-jgqf-hwc5-hh37 affects the following packages: send (npm). Ecosystems affected: npm.

How do I fix GHSA-jgqf-hwc5-hh37?

Update send to 0.11.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jgqf-hwc5-hh37 is resolved across your whole dependency graph.

How do I detect GHSA-jgqf-hwc5-hh37 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for send. 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-jgqf-hwc5-hh37 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-jgqf-hwc5-hh37?

O3 pinpoints whether GHSA-jgqf-hwc5-hh37 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-jgqf-hwc5-hh37 actively exploited in the wild?

No public exploit code has been indexed for GHSA-jgqf-hwc5-hh37 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-jgqf-hwc5-hh37 published, and has it been updated?

GHSA-jgqf-hwc5-hh37 was published on October 24, 2017 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-jgqf-hwc5-hh37

MEDIUM

GHSA-jgqf-hwc5-hh37 is a medium-severity (CVSS 5.3) vulnerability in send. O3 Security confirms whether GHSA-jgqf-hwc5-hh37 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Root Path Disclosure in send

Also known asCVE-2015-8859

Published

Oct 24, 2017

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

sendnpm

137.9Mdownloads / week

Description

Versions of send prior to 0.11.2 are affected by an information leakage vulnerability which may allow an attacker to enumerate paths on the server filesystem.

Recommendation

Update to version 0.11.1 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`send`	all versions	0.11.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for send. 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 send to 0.11.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jgqf-hwc5-hh37 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-jgqf-hwc5-hh37 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-jgqf-hwc5-hh37. 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 `send` prior to 0.11.2 are affected by an information leakage vulnerability which may allow an attacker to enumerate paths on the server filesystem. ## Recommendation Update to version 0.11.1 or later.

O3 Security · Impact-Aware SCA

Is GHSA-jgqf-hwc5-hh37 in your dependencies?

O3 detects GHSA-jgqf-hwc5-hh37 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