# CVE-2006-0052: Denial of service in n/a

> Remote attackers can cause mailing list delivery failure via a crafted multipart MIME message in Mailman's attachment scrubber.

- **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:** 31 Mar 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-1027-1, GHSA-f27j-9fv2-5hrg, RHSA-2006:0486

## What is CVE-2006-0052?

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

### Official description

The attachment scrubber (Scrubber.py) in Mailman 2.1.5 and earlier, when using Python's library email module 2.5, allows remote attackers to cause a denial of service (mailing list delivery failure) via a multipart MIME message with a single part that has two blank lines between the first boundary and the end boundary.

## Which versions are affected by CVE-2006-0052?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mailman` | Red Hat:enterprise_linux:3::as | All versions | 3:2.1.5.1-25.rhel3.5 |
| `mailman-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 3:2.1.5.1-25.rhel3.5 |
| `mailman` | Red Hat:enterprise_linux:3::desktop | All versions | 3:2.1.5.1-25.rhel3.5 |
| `mailman-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 3:2.1.5.1-25.rhel3.5 |
| `mailman` | Red Hat:enterprise_linux:3::es | All versions | 3:2.1.5.1-25.rhel3.5 |
| `mailman-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 3:2.1.5.1-25.rhel3.5 |
| `mailman` | Red Hat:enterprise_linux:3::ws | All versions | 3:2.1.5.1-25.rhel3.5 |
| `mailman-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 3:2.1.5.1-25.rhel3.5 |
| `mailman` | Red Hat:enterprise_linux:4::as | All versions | 3:2.1.5.1-34.rhel4.3 |
| `mailman-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 3:2.1.5.1-34.rhel4.3 |
| `mailman` | Red Hat:enterprise_linux:4::desktop | All versions | 3:2.1.5.1-34.rhel4.3 |
| `mailman-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 3:2.1.5.1-34.rhel4.3 |
| `mailman` | Red Hat:enterprise_linux:4::es | All versions | 3:2.1.5.1-34.rhel4.3 |
| `mailman-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 3:2.1.5.1-34.rhel4.3 |
| `mailman` | Red Hat:enterprise_linux:4::ws | All versions | 3:2.1.5.1-34.rhel4.3 |
| `mailman-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 3:2.1.5.1-34.rhel4.3 |

Products: Gnu Mailman.

## How do I fix CVE-2006-0052?

Upgrade to a fixed version.

## Is CVE-2006-0052 being exploited?

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

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

## Sources

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

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