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

> Attackers can overwrite or create arbitrary files in NeoFiler Android apps via directory traversal, potentially compromising device integrity.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 12 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-gqmg-xmq4-jwch

## What is CVE-2014-0805?

CVE-2014-0805 is a medium-severity path traversal vulnerability in n/a, published on 12 Jan 2014. 

### Official description

Directory traversal vulnerability in the NeoFiler application 5.4.3 and earlier, NeoFiler Free application 5.4.3 and earlier, and NeoFiler Lite application 2.4.2 and earlier for Android allows attackers to overwrite or create arbitrary files via unspecified vectors.

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

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

It affects 1 product.


Products: Skyarts Neofiler.

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

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

## Is CVE-2014-0805 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-0805 is a medium-severity path traversal vulnerability in n/a, published on 12 Jan 2014. 
Exploitation: There is no known exploitation of CVE-2014-0805 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-0805/ (Markdown: https://insights.sbomify.com/CVE-2014-0805/index.md)
```

## Sources

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

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