# CVE-2015-4641: Path traversal in n/a

> Remote attackers can execute arbitrary code with elevated privileges via directory traversal in SwiftKey language pack updates on Samsung devices.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-89p8-prmx-639j

## What is CVE-2015-4641?

CVE-2015-4641 is a medium-severity path traversal vulnerability in n/a, published on 19 Jun 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in the SwiftKey language-pack update implementation on Samsung Galaxy S4, S4 Mini, S5, and S6 devices allows remote web servers to write to arbitrary files, and consequently execute arbitrary code in a privileged context, by leveraging control of the skslm.swiftkey.net domain name and providing a .. (dot dot) in an entry in a ZIP archive, as demonstrated by a traversal to the /data/dalvik-cache directory.

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

## Which versions are affected by CVE-2015-4641?

It affects 1 product.


Products: Swiftkey Swiftkey Sdk.

## How do I fix CVE-2015-4641?

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

## Is CVE-2015-4641 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-4640](https://insights.sbomify.com/CVE-2015-4640/): Other in n/a (low 2.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-4641 and fix it if it is affected.

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

## Sources

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

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