# CVE-2006-4574: Integer overflow in n/a

> Remote attackers can cause a denial of service crash in Wireshark via an off-by-one error in the MIME Multipart dissector.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Oct 2006
- **Updated:** 17 Jan 2025
- **Also known as:** DEBIAN-CVE-2006-4574, GHSA-cjqf-4m3m-v7rh

## What is CVE-2006-4574?

CVE-2006-4574 is a high-severity vulnerability in Wireshark Wireshark, published on 28 Oct 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Off-by-one error in the MIME Multipart dissector in Wireshark (formerly Ethereal) 0.10.1 through 0.99.3 allows remote attackers to cause a denial of service (crash) via certain vectors that trigger an assertion error related to unexpected length values.

Weakness: CWE-617 (Reachable Assertion), CWE-193 (Off-by-one Error)

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

It affects 1 product.


Products: Wireshark Wireshark.

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

Upgrade to a fixed version.

## Is CVE-2006-4574 being exploited?

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

## Other vulnerabilities in Wireshark Wireshark

- [CVE-2011-0444](https://insights.sbomify.com/CVE-2011-0444/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-2994](https://insights.sbomify.com/CVE-2010-2994/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-2995](https://insights.sbomify.com/CVE-2010-2995/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-1266](https://insights.sbomify.com/CVE-2009-1266/): Other in n/a (critical 10.0)
- [CVE-2009-1210](https://insights.sbomify.com/CVE-2009-1210/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-4574 and fix it if it is affected.

What it is: CVE-2006-4574 is a high-severity vulnerability in Wireshark Wireshark, published on 28 Oct 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-4574 in the wild and no public exploit code.

Affected product: Wireshark Wireshark. 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-4574/ (Markdown: https://insights.sbomify.com/CVE-2006-4574/index.md)
```

## Sources

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

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