# CVE-2005-3573: Denial of service in n/a

> Remote attackers can crash the Mailman application by sending emails with specially crafted UTF-8 attachment filenames.

- **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:** 16 Nov 2005
- **Updated:** 7 Aug 2024
- **Also known as:** CVE-2005-3597, GHSA-p59g-55fw-7q46

## What is CVE-2005-3573?

CVE-2005-3573 is a medium-severity denial of service vulnerability in n/a, published on 16 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Scrubber.py in Mailman 2.1.5-8 does not properly handle UTF8 character encodings in filenames of e-mail attachments, which allows remote attackers to cause a denial of service (application crash).

## Which versions are affected by CVE-2005-3573?

It affects 1 product.


Products: Gnu Mailman.

## How do I fix CVE-2005-3573?

Upgrade to a fixed version.

## Is CVE-2005-3573 being exploited?

There is no known exploitation of CVE-2005-3573 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-2005-3573 and fix it if it is affected.

What it is: CVE-2005-3573 is a medium-severity denial of service vulnerability in n/a, published on 16 Nov 2005. 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-2005-3573 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-2005-3573/ (Markdown: https://insights.sbomify.com/CVE-2005-3573/index.md)
```

## Sources

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

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