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

> Remote attackers can write to arbitrary files via directory traversal in the S-Link SLFileManager Android application.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 26 Sep 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9rgq-2f3r-j439

## What is CVE-2014-5319?

CVE-2014-5319 is a medium-severity path traversal vulnerability in n/a, published on 26 Sep 2014. It can be exploited over the network.

### Official description

Directory traversal vulnerability in the S-Link SLFileManager application 1.2.5 and earlier for Android allows remote attackers to write to files via unspecified vectors.

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

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

It affects 1 product.


Products: S-Link Slfilemanager.

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

No fix has been published for CVE-2014-5319 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-5319 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-5319 is a medium-severity path traversal vulnerability in n/a, published on 26 Sep 2014. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2014-5319 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-5319/ (Markdown: https://insights.sbomify.com/CVE-2014-5319/index.md)
```

## Sources

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

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