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

> Remote attackers can enumerate valid usernames by analyzing distinct error messages from the web mail service.

- **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:** 18 May 2005
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-qpwh-qx3h-p3rq

## What is CVE-2005-1650?

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

### Official description

The web mail service in Woppoware PostMaster 4.2.2 (build 3.2.5) generates different error messages depending on whether a user exists or not, which allows remote attackers to determine valid usernames.

Weakness: CWE-203 (Observable Discrepancy)

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

It affects 1 product.


Products: Woppoware Postmaster.

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

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

## Is CVE-2005-1650 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-1651](https://insights.sbomify.com/CVE-2005-1651/): Path traversal in n/a (high 7.5)
- [CVE-2005-1652](https://insights.sbomify.com/CVE-2005-1652/): Auth bypass in n/a (high 7.5)
- [CVE-2005-1653](https://insights.sbomify.com/CVE-2005-1653/): Cross-site scripting in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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