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

> Remote attackers can bypass file whitelists and access sensitive information by exploiting path normalization flaws in the Plack::App::File component.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Sep 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-5269, DLA-61-1, GHSA-vx87-xj55-ccgc, MGASA-2014-0486

## What is CVE-2014-5269?

CVE-2014-5269 is a medium-severity path traversal vulnerability in n/a, published on 4 Sep 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Plack::App::File in Plack before 1.0031 removes trailing slash characters from paths, which allows remote attackers to bypass the whitelist of generated files and obtain sensitive information via a crafted path, related to Plack::Middleware::Static.

Weakness: CWE-264

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

It affects 1 product.


Products: Plack Project Plack.

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

Upgrade to a fixed version.

## Is CVE-2014-5269 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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