# CVE-2009-4377: Null dereference in n/a

> Remote attackers can crash Wireshark via crafted SMB packets due to a NULL pointer dereference in the dissectors.

- **Severity:** Medium 4.3 (`AV:N/AC:M/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:** 21 Dec 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-4377, GHSA-wqc7-2v82-hg6w

## What is CVE-2009-4377?

CVE-2009-4377 is a medium-severity vulnerability in Wireshark Wireshark, published on 21 Dec 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The (1) SMB and (2) SMB2 dissectors in Wireshark 0.9.0 through 1.2.4 allow remote attackers to cause a denial of service (crash) via a crafted packet that triggers a NULL pointer dereference, as demonstrated by fuzz-2009-12-07-11141.pcap.

## Which versions are affected by CVE-2009-4377?

It affects 1 product.


Products: Wireshark Wireshark.

## How do I fix CVE-2009-4377?

Upgrade to a fixed version.

## Is CVE-2009-4377 being exploited?

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

What it is: CVE-2009-4377 is a medium-severity vulnerability in Wireshark Wireshark, published on 21 Dec 2009. 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-2009-4377 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-2009-4377/ (Markdown: https://insights.sbomify.com/CVE-2009-4377/index.md)
```

## Sources

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

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