# CVE-2002-1731: Information disclosure in n/a

> Local users can list valid user accounts via the System Request menu, exposing sensitive account information.

- **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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jun 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-wpc7-rpjv-rv8j

## What is CVE-2002-1731?

CVE-2002-1731 is a low-severity vulnerability in n/a, published on 21 Jun 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The System Request menu in IBM AS/400 allows local users to list valid user accounts by viewing the object names that are type USRPRF.

## Which versions are affected by CVE-2002-1731?

It affects 1 product.


Products: Ibm Os 400.

## How do I fix CVE-2002-1731?

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

## Is CVE-2002-1731 being exploited?

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

Public exploit code:

- OS/400 - User Account Name Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-6836](https://insights.sbomify.com/CVE-2006-6836/): Other in n/a (critical 10.0)
- [CVE-2007-3537](https://insights.sbomify.com/CVE-2007-3537/): Information disclosure in n/a (high 7.8)
- [CVE-2007-0442](https://insights.sbomify.com/CVE-2007-0442/): Other in n/a (medium 5.0)
- [CVE-2005-1182](https://insights.sbomify.com/CVE-2005-1182/): Denial of service in n/a (medium 5.0)
- [CVE-2008-2709](https://insights.sbomify.com/CVE-2008-2709/): Memory corruption in n/a (medium 4.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1731 and fix it if it is affected.

What it is: CVE-2002-1731 is a low-severity vulnerability in n/a, published on 21 Jun 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-1731 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-2002-1731/ (Markdown: https://insights.sbomify.com/CVE-2002-1731/index.md)
```

## Sources

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

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