Process crash via unchecked MSMMS length arithmetic
Published Jun 7, 2023 · Updated Nov 3, 2025
Heap buffer over-read in Wireshark 4.0.5 and earlier allows context-dependent attackers to crash the process via crafted MSMMS packets. The MSMMS dissector derives length_remaining from a packet field, passes a four-byte UTF-16 slice that finalizes into three bytes, then directs format_text to read four bytes. The public reproducer triggers the error only under fuzzshark, not TShark, and NVD bounds the published impact to a process crash requiring user interaction.
Summary
What happened
Heap buffer over-read in Wireshark 4.0.5 and earlier allows context-dependent attackers to crash the process via crafted MSMMS packets. The MSMMS dissector derives length_remaining from a packet field, passes a four-byte UTF-16 slice that finalizes into three bytes, then directs format_text to read four bytes. The public reproducer triggers the error only under fuzzshark, not TShark, and NVD bounds the published impact to a process crash requiring user interaction.
The record
- CVE
- CVE-2023-0667
- Published
- Jun 7, 2023
- Updated
- Nov 3, 2025
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- CWE-787, CWE-122
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 7, 2023CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=3.6.13
- Affected versionversion=0 <=4.0.5
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- AHA! fuzzshark MSMMS reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo