# CVE-2010-0304: Memory corruption in n/a

> Remote attackers can crash Wireshark via malformed packets due to buffer overflows in the LWRES dissector, requiring an upgrade to mitigate.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Feb 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-0304, GHSA-jpr3-gg36-wv7f

## What is CVE-2010-0304?

CVE-2010-0304 is a high-severity memory corruption vulnerability in Wireshark Wireshark, published on 3 Feb 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple buffer overflows in the LWRES dissector in Wireshark 0.9.15 through 1.0.10 and 1.2.0 through 1.2.5 allow remote attackers to cause a denial of service (crash) via a malformed packet, as demonstrated using a stack-based buffer overflow to the dissect_getaddrsbyname_request function.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2010-0304?

It affects 1 product.


Products: Wireshark Wireshark.

## How do I fix CVE-2010-0304?

Upgrade to a fixed version.

## Is CVE-2010-0304 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-0304 exists.

Public exploit code:

- Wireshark LWRES Dissector getaddrsbyname_request Buffer Overflow (metasploit)
- Wireshark LWRES Dissector getaddrsbyname_request Buffer Overflow (loop) (metasploit)
- Wireshark 1.2.5 - 'LWRES getaddrbyname' Stack Buffer Overflow (PoC) (exploitdb)
- Wireshark - LWRES Dissector getaddrsbyname_request Buffer Overflow (Metasploit) (exploitdb)
- Wireshark - LWRES Dissector getaddrsbyname_request Buffer Overflow (Loop) (Metasploit) (exploitdb)

## 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-2010-0304 and fix it if it is affected.

What it is: CVE-2010-0304 is a high-severity memory corruption vulnerability in Wireshark Wireshark, published on 3 Feb 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-0304 exists.

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-2010-0304/ (Markdown: https://insights.sbomify.com/CVE-2010-0304/index.md)
```

## Sources

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

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