# CVE-2006-5487: Path traversal in n/a

> Remote attackers can write arbitrary files via directory traversal in ARJ archives, potentially leading to code execution on MailMarshal SMTP servers.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pmm9-ffgf-jpqg

## What is CVE-2006-5487?

CVE-2006-5487 is a critical path traversal vulnerability in n/a, published on 10 Nov 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in Marshal MailMarshal SMTP 5.x, 6.x, and 2006, and MailMarshal for Exchange 5.x, allows remote attackers to write arbitrary files via ".." sequences in filenames in an ARJ compressed archive.

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

## Which versions are affected by CVE-2006-5487?

It affects 1 product.


Products: Marshal Mailmarshal Smtp.

## How do I fix CVE-2006-5487?

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

## Is CVE-2006-5487 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-5487 and fix it if it is affected.

What it is: CVE-2006-5487 is a critical path traversal vulnerability in n/a, published on 10 Nov 2006. 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-2006-5487 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-2006-5487/ (Markdown: https://insights.sbomify.com/CVE-2006-5487/index.md)
```

## Sources

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

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