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

> Local attackers can exploit symlink vulnerabilities in temporary file creation to read sensitive information or write to arbitrary files.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Oct 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-2277, GHSA-g7r2-wjmp-vjj6, MGASA-2014-0147

## What is CVE-2014-2277?

CVE-2014-2277 is a high-severity path traversal vulnerability in n/a, published on 17 Oct 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The make_temporary_filename function in perltidy 20120701-1 and earlier allows local users to obtain sensitive information or write to arbitrary files via a symlink attack, related to use of the tmpnam function.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Perltidy Project Perltidy.

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

Upgrade to a fixed version.

## Is CVE-2014-2277 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-10374](https://insights.sbomify.com/CVE-2016-10374/): Path traversal in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-2277 is a high-severity path traversal vulnerability in n/a, published on 17 Oct 2017. 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-2014-2277 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-2277/ (Markdown: https://insights.sbomify.com/CVE-2014-2277/index.md)
```

## Sources

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

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