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

> Remote attackers can enumerate valid user IDs on the IBM iSeries AS/400 POP3 server due to distinct error messages for existing and non-existing users.

- **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:** 16 Apr 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-j238-9q39-h4gr

## What is CVE-2005-1133?

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

### Official description

The POP3 server in IBM iSeries AS/400 returns different error messages when the user exists or not, which allows remote attackers to determine valid user IDs on the server.

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

It affects 1 product.


Products: Ibm Iseries as 400.

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

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

## Is CVE-2005-1133 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-1238](https://insights.sbomify.com/CVE-2005-1238/): Path traversal in n/a (high 7.5)
- [CVE-2005-1025](https://insights.sbomify.com/CVE-2005-1025/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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