# CVE-2023-0667: Wireshark MSMMS parsing buffer overflow

> An attacker can trigger a heap-based buffer overflow in Wireshark via crafted MSMMS packets, potentially executing code in the application context.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 7 Jun 2023
- **Updated:** 3 Nov 2025
- **Also known as:** AZL-27144, DEBIAN-CVE-2023-0667, GHSA-m7h5-4hfx-r2mh, OESA-2023-1363, OESA-2023-1371, OESA-2023-1372, UBUNTU-CVE-2023-0667, openSUSE-SU-2024:13014-1

## What is CVE-2023-0667?

CVE-2023-0667 is a medium-severity memory corruption vulnerability in Wireshark Wireshark, published on 7 Jun 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Due to failure in validating the length provided by an attacker-crafted MSMMS packet, Wireshark version 4.0.5 and prior, in an unusual configuration, is susceptible to a heap-based buffer overflow, and possibly code execution in the context of the process running Wireshark

Weakness: CWE-787 (Out-of-bounds Write), CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2023-0667?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wireshark` | openSUSE:Tumbleweed | All versions | 4.0.6-3.1 |

Products: Wireshark Wireshark.

## How do I fix CVE-2023-0667?

Upgrade to a fixed version.

## Is CVE-2023-0667 being exploited?

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

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

What it is: CVE-2023-0667 is a medium-severity memory corruption vulnerability in Wireshark Wireshark, published on 7 Jun 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-0667 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-2023-0667/ (Markdown: https://insights.sbomify.com/CVE-2023-0667/index.md)
```

## Sources

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

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