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

> Remote attackers can write arbitrary files via directory traversal in CHM files, requiring user interaction to open the malicious file.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **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:** Yes
- **Published:** 23 Feb 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-1589, GHSA-pmjm-c5h8-vf2q, UBUNTU-CVE-2015-1589

## What is CVE-2015-1589?

CVE-2015-1589 is a medium-severity path traversal vulnerability in n/a, published on 23 Feb 2015. 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 arCHMage 0.2.4 allows remote attackers to write to arbitrary files via a .. (dot dot) in a CHM file.

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

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

It affects 1 product.


Products: Archmage Project Archmage.

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

Upgrade to a fixed version.

## Is CVE-2015-1589 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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