# CVE-2003-0902: Command injection in n/a

> Remote attackers can execute arbitrary commands on minimalist mailing list manager installations, requiring immediate patching.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Jan 2004
- **Updated:** 17 Sep 2024
- **Also known as:** DSA-402, GHSA-6g6q-m8px-jr9g

## What is CVE-2003-0902?

CVE-2003-0902 is a high-severity command injection vulnerability in n/a, published on 14 Jan 2004. It can be exploited over the network, with no action from the victim.

### Official description

Unknown vulnerability in minimalist mailing list manager 2.4, 2.2, and possibly other versions, allows remote attackers to execute arbitrary commands.

## Which versions are affected by CVE-2003-0902?

It affects 1 product.


Products: Minimalist Minimalist.

## How do I fix CVE-2003-0902?

Apply the vendor's patch.

## Is CVE-2003-0902 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0902 and fix it if it is affected.

What it is: CVE-2003-0902 is a high-severity command injection vulnerability in n/a, published on 14 Jan 2004. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2003-0902 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-2003-0902/ (Markdown: https://insights.sbomify.com/CVE-2003-0902/index.md)
```

## Sources

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

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