# CVE-2014-6394: Directory Traversal in send

> Remote attackers can access restricted directories outside the document root due to flawed path verification in the Node.js send library.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** CLSA-2026-1793287341, DEBIAN-CVE-2014-6394, GHSA-xwg4-93c6-3h42, UBUNTU-CVE-2014-6394

## What is CVE-2014-6394?

CVE-2014-6394 is a high-severity path traversal vulnerability in Apple Xcode, published on 8 Oct 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

visionmedia send before 0.8.4 for Node.js uses a partial comparison for verifying whether a directory is within the document root, which allows remote attackers to access restricted directories, as demonstrated using "public-restricted" under a "public" directory.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2014-6394?

2 open source packages ship an affected version, including send. It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `send` | npm | All versions | 0.8.4 |
| `send` | npm | All versions | 0.8.4 |

Products: Apple Xcode, Fedoraproject Fedora, Joyent Node.js.

## How do I fix CVE-2014-6394?

Upgrade send to 0.8.4 or later.

## Is CVE-2014-6394 being exploited?

There is no known exploitation of CVE-2014-6394 in the wild and no public exploit code.

## Other vulnerabilities in Apple Xcode

- [CVE-2025-48384](https://insights.sbomify.com/CVE-2025-48384/): Git Link Following (high 8.1, exploited in the wild)
- [CVE-2014-9390](https://insights.sbomify.com/CVE-2014-9390/): JGit Improper Input Validation vulnerability (critical 9.8)
- [CVE-2019-14379](https://insights.sbomify.com/CVE-2019-14379/): Deserialization of untrusted data in FasterXML jackson-databind (critical 9.8)
- [CVE-2018-4164](https://insights.sbomify.com/CVE-2018-4164/): An issue was discovered in certain Apple products. (critical 9.8)
- [CVE-2016-0746](https://insights.sbomify.com/CVE-2016-0746/): Use after free in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-6394 and fix it if it is affected.

What it is: CVE-2014-6394 is a high-severity path traversal vulnerability in Apple Xcode, published on 8 Oct 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-6394 in the wild and no public exploit code.

Affected packages and fixed versions:
- send (npm): affected all versions; fixed in 0.8.4
- send (npm): affected all versions; fixed in 0.8.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-6394/ (Markdown: https://insights.sbomify.com/CVE-2014-6394/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-6394
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-6394
- OSV: https://osv.dev/vulnerability/CVE-2014-6394

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-6394/
Summaries are generated and may contain mistakes; the official description above is the record.