Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2023-0667: CWE-122 Heap-based Buffer Overflow in Wireshark Foundation Wireshark

0
Medium
VulnerabilityCVE-2023-0667cvecve-2023-0667cwe-122
Published: Wed Jun 07 2023 (06/07/2023, 02:38:07 UTC)
Source: CVE Database V5
Vendor/Project: Wireshark Foundation
Product: Wireshark

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

AI-Powered Analysis

AILast updated: 11/04/2025, 00:07:31 UTC

Technical Analysis

CVE-2023-0667 is a heap-based buffer overflow vulnerability identified in Wireshark Foundation's Wireshark software, specifically affecting versions 4.0.5 and earlier. The vulnerability stems from a failure to properly validate the length field in MSMMS protocol packets, which are processed by Wireshark during packet dissection. An attacker can craft a malicious MSMMS packet with an incorrect length value that causes Wireshark to allocate insufficient memory and subsequently write beyond the allocated heap buffer. This memory corruption can lead to a crash of the Wireshark process, resulting in a denial of service. In certain configurations and under specific conditions, this overflow could be leveraged to execute arbitrary code within the context of the user running Wireshark. Exploitation requires that the victim opens a malicious capture file or receives malicious network traffic that Wireshark analyzes. No privileges are required to exploit this vulnerability, but user interaction is necessary. The vulnerability has a CVSS 3.1 base score of 6.5, reflecting network attack vector, low attack complexity, no privileges required, but requiring user interaction and impacting availability. No public exploits have been reported yet, and no patches were linked at the time of reporting, indicating that remediation may be pending. The vulnerability is classified under CWE-122, indicating a heap-based buffer overflow issue. This flaw highlights the risks associated with parsing complex network protocols without rigorous input validation in widely used network analysis tools.

Potential Impact

For European organizations, the primary impact of CVE-2023-0667 is the potential disruption of network monitoring and forensic analysis capabilities due to Wireshark crashes or instability. This can hinder incident response and network troubleshooting efforts, especially in security operations centers (SOCs) and critical infrastructure environments that rely heavily on Wireshark for packet inspection. Although code execution is possible, it is less likely given the complexity and user interaction required, reducing the risk of widespread compromise. However, successful exploitation could allow attackers to execute arbitrary code with the privileges of the Wireshark user, potentially leading to further system compromise if the user has elevated rights. The availability impact may also affect organizations during active incident investigations, delaying detection and mitigation of other threats. European entities in sectors such as telecommunications, finance, energy, and government, which frequently use Wireshark for network diagnostics, could face operational disruptions. Additionally, the vulnerability could be leveraged in targeted attacks against security analysts or researchers if malicious capture files are shared or downloaded from untrusted sources.

Mitigation Recommendations

1. Monitor Wireshark Foundation announcements and promptly apply official patches or updates addressing CVE-2023-0667 once released. 2. Until patches are available, avoid opening untrusted or suspicious capture files, especially those containing MSMMS protocol data. 3. Implement strict network segmentation and firewall rules to limit exposure of systems running Wireshark to untrusted networks or sources. 4. Use sandboxing or isolated environments for analyzing unknown capture files to contain potential exploitation. 5. Educate security analysts and network engineers on the risks of opening unverified capture files and encourage verification of file provenance. 6. Employ endpoint protection solutions that can detect anomalous behavior or crashes related to Wireshark processes. 7. Consider alternative packet analysis tools or updated versions that do not exhibit this vulnerability for critical operations. 8. Regularly audit and restrict user privileges to minimize the impact of potential code execution within Wireshark's process context.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
AHA
Date Reserved
2023-02-03T22:08:34.816Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69092629fe7723195e0b5ce1

Added to database: 11/3/2025, 10:01:13 PM

Last enriched: 11/4/2025, 12:07:31 AM

Last updated: 2/7/2026, 3:50:45 PM

Views: 17

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats