# CVE-2014-3127: Path traversal in n/a

> Remote attackers can modify files outside intended directories via crafted source packages due to a path traversal vulnerability in dpkg.

- **Severity:** High 7.1 (`AV:N/AC:H/Au:N/C:N/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-3127, GHSA-f267-j9wx-cwjf, UBUNTU-CVE-2014-3127

## What is CVE-2014-3127?

CVE-2014-3127 is a high-severity path traversal vulnerability in n/a, published on 14 May 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

dpkg 1.15.9 on Debian squeeze introduces support for the "C-style encoded filenames" feature without recognizing that the squeeze patch program lacks this feature, which triggers an interaction error that allows remote attackers to conduct directory traversal attacks and modify files outside of the intended directories via a crafted source package.  NOTE: this can be considered a release engineering problem in the effort to fix CVE-2014-0471.

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

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

It affects 1 product.


Products: Debian Dpkg.

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

Apply the vendor's patch.

## Is CVE-2014-3127 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-8283](https://insights.sbomify.com/CVE-2017-8283/): Path traversal in n/a (critical 9.8)
- [CVE-2025-6297](https://insights.sbomify.com/CVE-2025-6297/): dpkg-deb: Fix cleanup for control member with restricted directories (high 8.2)
- [CVE-2026-2219](https://insights.sbomify.com/CVE-2026-2219/): Denial of service in dpkg (high 7.5)
- [CVE-2004-2768](https://insights.sbomify.com/CVE-2004-2768/): Privilege escalation in n/a (high 7.2)
- [CVE-2014-8625](https://insights.sbomify.com/CVE-2014-8625/): Memory corruption in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-3127 is a high-severity path traversal vulnerability in n/a, published on 14 May 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-3127 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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