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

> Local attackers can read private mailing list archives due to predictable filenames in world-executable directories.

- **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:** Yes
- **Published:** 2 Apr 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-pvv2-68cw-w39c

## What is CVE-2002-0389?

CVE-2002-0389 is a low-severity vulnerability in n/a, published on 2 Apr 2003. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Pipermail in Mailman stores private mail messages with predictable filenames in a world-executable directory, which allows local users to read private mailing list archives.

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

It affects 1 product.


Products: Gnu Mailman.

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

Apply the vendor's patch.

## Is CVE-2002-0389 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-6893](https://insights.sbomify.com/CVE-2016-6893/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2016-7123](https://insights.sbomify.com/CVE-2016-7123/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2005-4153](https://insights.sbomify.com/CVE-2005-4153/): Denial of service in n/a (high 7.8)
- [CVE-2006-2191](https://insights.sbomify.com/CVE-2006-2191/): Other in n/a (high 7.5)
- [CVE-2004-1143](https://insights.sbomify.com/CVE-2004-1143/): Weak cryptography in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-0389 is a low-severity vulnerability in n/a, published on 2 Apr 2003. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-0389 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-2002-0389/ (Markdown: https://insights.sbomify.com/CVE-2002-0389/index.md)
```

## Sources

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

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