# CVE-2003-0991: Denial of service in n/a

> Remote attackers can crash the Mailman mailing list server by sending malformed email commands, causing a denial of service.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-5vf7-m49c-hv97

## What is CVE-2003-0991?

CVE-2003-0991 is a medium-severity denial of service vulnerability in Sgi Propack, published on 1 Sep 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unknown vulnerability in the mail command handler in Mailman before 2.0.14 allows remote attackers to cause a denial of service (crash) via malformed e-mail commands.

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

It affects 2 products.


Products: Gnu Mailman, Sgi Propack.

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

Upgrade to a fixed version.

## Is CVE-2003-0991 being exploited?

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

## Other vulnerabilities in Sgi Propack

- [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-2003-0991 and fix it if it is affected.

What it is: CVE-2003-0991 is a medium-severity denial of service vulnerability in Sgi Propack, published on 1 Sep 2004. 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-2003-0991 in the wild and no public exploit code.

Affected product: Sgi Propack. 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-0991/ (Markdown: https://insights.sbomify.com/CVE-2003-0991/index.md)
```

## Sources

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

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