# CVE-2005-1754: Path traversal in n/a

> Remote attackers can read arbitrary files via path traversal in JavaMail API, though vendors dispute the vulnerability's existence.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h69g-x235-8mrr

## What is CVE-2005-1754?

CVE-2005-1754 is a medium-severity path traversal vulnerability in n/a, published on 21 May 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

JavaMail API 1.1.3 through 1.3, as used by Apache Tomcat 5.0.16, allows remote attackers to read arbitrary files via a full pathname in the argument to the Download parameter.  NOTE: Sun and Apache dispute this issue.  Sun states: "The report makes references to source code and files that do not exist in the mentioned products.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2005-1754?

It affects 2 products.


Products: Apache Tomcat Apache Tomcat, Sun Javamail.

## How do I fix CVE-2005-1754?

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

## Is CVE-2005-1754 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1754 exists.

Public exploit code:

- Sun JavaMail 1.x - Multiple Information Disclosure Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1754 and fix it if it is affected.

What it is: CVE-2005-1754 is a medium-severity path traversal vulnerability in n/a, published on 21 May 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1754 exists.

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-2005-1754/ (Markdown: https://insights.sbomify.com/CVE-2005-1754/index.md)
```

## Sources

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

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