Skip to main content
VulnerabilityPublished Updated

CVE-2023-2906: Wireshark · Divide By Zero

Affects WiresharkSource CVE Database V5

0

Not known to be exploited.

Data as of 26 Oct 2026, 15:59 UTC

Severity
Medium

Rated Medium by the CNA (AHA) · No CVSS score from NVD or the CNA

EPSS
2.7% chance of exploitation in 30 days – higher than 86% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Aug 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

Affected software

ProductAffectedFixed in
GitHubwireshark/wiresharkpkg:github/wireshark/wiresharkOther threatsAffected
  • =2.0.0
  • <=4.0.7
Fixed in–

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

AI-suggested

Users should check the Wireshark Foundation's official advisories for updates or patches addressing this vulnerability. Until a fix is available, avoid processing untrusted CP2179 packets or use alternative methods to analyze such traffic.

Description

Wireshark versions 2.0.0 through 4.0.7 contain a divide-by-zero vulnerability due to improper validation of the length field in CP2179 packets. This flaw can be triggered by an attacker crafting a malicious packet, leading to a denial of service condition in the affected software.

References

Community reviews

Loading reviews…