Skip to main content
VulnerabilityPublished Updated

CVE-2023-0668: Wireshark · Out-of-bounds Read

Affects WiresharkSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium : upgrade to 4.0.6 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
2.2% chance of exploitation in 30 days – higher than 82% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.0.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Jun 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade wireshark/wireshark to 4.0.6.

Affected software

ProductAffectedFixed in
GitHubwireshark/wiresharkpkg:github/wireshark/wiresharkOther threatsAffected
  • <4.0.6
Fixed in
  • 4.0.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Update Wireshark to the latest version as soon as a patch addressing CVE-2023-0668 is released by the Wireshark Foundation.
  2. If you cannot patch yet, avoid opening untrusted or unauthenticated capture files, especially those containing IEEE-C37.118 protocol data.
  3. Implement network segmentation and filtering to limit exposure of Wireshark analysis systems to untrusted network traffic that could contain malicious packets.
  4. Use sandboxing or isolated virtual machines for running Wireshark to contain potential exploitation impact.
  5. Educate network analysts and security teams about the risk of opening suspicious capture files and enforce strict file validation policies.
  6. 7. Employ endpoint detection and response (EDR) tools to detect anomalous behavior on analyst workstations that could indicate exploitation attempts. 8. For critical infrastructure operators using IEEE-C37.118, consider additional protocol-level filtering or validation to detect malformed packets before they reach analysis tools.

Description

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

References

Community reviews

Loading reviews…