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

> Remote attackers can read the last line of the shadow file via a long user field in chetcpasswd.cgi, exposing sensitive password hashes.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Dec 2006
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-rw97-jv7j-3v6x

## What is CVE-2002-2219?

CVE-2002-2219 is a high-severity vulnerability in n/a, published on 21 Dec 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

chetcpasswd.cgi in Pedro Lineu Orso chetcpasswd before 2.1 allows remote attackers to read the last line of the shadow file via a long user (userid) field.

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

It affects 1 product.


Products: Chetcpasswd Chetcpasswd.

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

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

## Is CVE-2002-2219 being exploited?

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

Public exploit code:

- CHETCPASSWD 1.12 - Shadow File Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-6681](https://insights.sbomify.com/CVE-2006-6681/): Denial of service in n/a (high 7.5)
- [CVE-2002-2220](https://insights.sbomify.com/CVE-2002-2220/): Memory corruption in n/a (medium 6.2)
- [CVE-2002-2221](https://insights.sbomify.com/CVE-2002-2221/): Privilege escalation in n/a (medium 6.2)
- [CVE-2006-6680](https://insights.sbomify.com/CVE-2006-6680/): Information disclosure in n/a (medium 4.6)
- [CVE-2006-6639](https://insights.sbomify.com/CVE-2006-6639/): Privilege escalation in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-2219 is a high-severity vulnerability in n/a, published on 21 Dec 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-2219 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-2219/ (Markdown: https://insights.sbomify.com/CVE-2002-2219/index.md)
```

## Sources

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

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