# CVE-2005-1682: Information disclosure in n/a

> Authenticated users can read other users' emails by manipulating message numbers in the JavaMail API.

- **Severity:** Low 2.1 (`AV:L/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:** 25 May 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-549v-j953-7rc4

## What is CVE-2005-1682?

CVE-2005-1682 is a low-severity vulnerability in n/a, published on 25 May 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

JavaMail API, as used by Solstice Internet Mail Server POP3 2.0, does not properly validate the message number in the MimeMessage constructor in javax.mail.internet.InternetHeaders, which allows remote authenticated users to read other users' e-mail messages by modifying the msgno parameter.  NOTE: Sun disputes this issue, stating "The report makes references to source code and files that do not exist in the mentioned products.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Solstice Solstice Internet Mail Server.

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

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

## Is CVE-2005-1682 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2005-1682 is a low-severity vulnerability in n/a, published on 25 May 2005. 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-1682 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-1682/ (Markdown: https://insights.sbomify.com/CVE-2005-1682/index.md)
```

## Sources

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

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