How severe is GHSA-xwg4-93c6-3h42?

No CVSS score has been assigned to GHSA-xwg4-93c6-3h42 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xwg4-93c6-3h42?

GHSA-xwg4-93c6-3h42 affects the following packages: send (npm). Ecosystems affected: npm.

How do I fix GHSA-xwg4-93c6-3h42?

Update send to 0.8.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xwg4-93c6-3h42 is resolved across your whole dependency graph.

How do I detect GHSA-xwg4-93c6-3h42 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-xwg4-93c6-3h42 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-xwg4-93c6-3h42?

O3 pinpoints whether GHSA-xwg4-93c6-3h42 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-xwg4-93c6-3h42 actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-xwg4-93c6-3h42, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What type of vulnerability is GHSA-xwg4-93c6-3h42?

GHSA-xwg4-93c6-3h42 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-xwg4-93c6-3h42 published, and has it been updated?

GHSA-xwg4-93c6-3h42 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-xwg4-93c6-3h42

GHSA-xwg4-93c6-3h42 is a Path Traversal vulnerability in send. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-xwg4-93c6-3h42 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Directory Traversal in send

Also known asCVE-2014-6394

Published

Oct 24, 2017

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Blast Radius

1 pkg affected

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

sendnpm

138.4Mdownloads / week

Description

Versions 0.8.3 and earlier of send are affected by a directory traversal vulnerability. When relying on the root option to restrict file access it may be possible for an application consumer to escape out of the restricted directory and access files in a similarly named directory.

For example, static(_dirname + '/public') would allow access to _dirname + '/public-restricted'.

Recommendation

Update to version 0.8.4 or later.

Affected Packages

1 total 1 fixed

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

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

visionmedia send before 0.8.4 for Node.js uses a partial comparison for …

github.comNVDSep 2017

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

Frequently Asked Questions

Versions 0.8.3 and earlier of `send` are affected by a directory traversal vulnerability. When relying on the root option to restrict file access it may be possible for an application consumer to escape out of the restricted directory and access files in a similarly named directory. For example, `static(_dirname + '/public')` would allow access to `_dirname + '/public-restricted'`. ## Recommendation Update to version 0.8.4 or later.

O3 Security · Impact-Aware SCA

Is GHSA-xwg4-93c6-3h42 in your dependencies?

O3 detects GHSA-xwg4-93c6-3h42 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