# CVE-2005-1753: Missing authorization in n/a

> Remote attackers can view other users' email attachments by directly requesting specific URLs, 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:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-g53q-h9jm-jgf9

## What is CVE-2005-1753?

CVE-2005-1753 is a medium-severity missing authorization vulnerability in n/a, published on 21 May 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ReadMessage.jsp in JavaMail API 1.1.3 through 1.3, as used by Apache Tomcat 5.0.16, allows remote attackers to view other users' e-mail attachments via a direct request to /mailboxesdir/username@domainname. 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-264

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

It affects 1 product.


Products: Sun Javamail.

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

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

## Is CVE-2005-1753 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-6059](https://insights.sbomify.com/CVE-2007-6059/): Denial of service in n/a (medium 5.0)
- [CVE-2005-1105](https://insights.sbomify.com/CVE-2005-1105/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-1753 is a medium-severity missing authorization vulnerability in n/a, published on 21 May 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-1753 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-2005-1753/ (Markdown: https://insights.sbomify.com/CVE-2005-1753/index.md)
```

## Sources

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

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