# CVE-2013-4116: Local Privilege Escalation in npm

> Local attackers can overwrite arbitrary files via symlink attacks on predictable temporary files during archive unpacking in npm.

- **Severity:** Low 3.3 (`AV:L/AC:M/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-4116, GHSA-v3jv-wrf4-5845

## What is CVE-2013-4116?

CVE-2013-4116 is a low-severity path traversal vulnerability in n/a, published on 22 Apr 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

lib/npm.js in Node Packaged Modules (npm) before 1.3.3 allows local users to overwrite arbitrary files via a symlink attack on temporary files with predictable names that are created when unpacking archives.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2013-4116?

2 open source packages ship an affected version, including npm. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `npm` | npm | All versions | 1.3.3 |
| `npm` | npm | All versions | 1.3.3 |

Products: Node Packaged Modules Project Node Packaged Modules.

## How do I fix CVE-2013-4116?

Upgrade npm to 1.3.3 or later.

## Is CVE-2013-4116 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4116 and fix it if it is affected.

What it is: CVE-2013-4116 is a low-severity path traversal vulnerability in n/a, published on 22 Apr 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-4116 in the wild and no public exploit code.

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

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-2013-4116/ (Markdown: https://insights.sbomify.com/CVE-2013-4116/index.md)
```

## Sources

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

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