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

> Remote attackers can overwrite or create arbitrary files in the Android Unzipper application via a crafted filename, requiring user interaction to open the malicious archive.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Mar 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7qpm-cp88-fc7h

## What is CVE-2014-1975?

CVE-2014-1975 is a medium-severity path traversal vulnerability in n/a, published on 18 Mar 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

Directory traversal vulnerability in the R-Company Unzipper application 1.0.1 and earlier for Android allows remote attackers to overwrite or create arbitrary files via a crafted filename.

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

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

It affects 1 product.


Products: R-Company Unzipper.

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

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

## Is CVE-2014-1975 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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