Skip to main content
VulnerabilityPublished Updated

CVE-2023-4512: Wireshark · Uncontrolled Recursion

Affects WiresharkSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 12:54 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 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
Debiandebian/wiresharkpkg:deb/debian/wiresharkOther threatsAffected
  • =4.0.0
Fixed in–
Fedorafedora/wiresharkpkg:rpm/fedora/wiresharkOther threatsAffected
  • =4.0.0
Fixed in–

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-4512 is released by the Wireshark Foundation.
  2. Until a patch is available, avoid opening capture files from untrusted or unknown sources to reduce the risk of triggering the vulnerability.
  3. Implement strict network segmentation and access controls to limit exposure of Wireshark instances to potentially malicious packet injections.
  4. Educate users and security analysts about the risks of opening suspicious capture files and encourage verification of file provenance.
  5. Use alternative network analysis tools or offline analysis methods when handling untrusted data.
  6. Monitor Wireshark usage logs and system stability to detect abnormal crashes that may indicate exploitation attempts.
  7. Employ endpoint protection solutions that can detect and block attempts to exploit application crashes or resource exhaustion.
  8. Regularly review and update incident response procedures to include scenarios involving denial of service against security monitoring tools.

Description

CBOR dissector crash in Wireshark 4.0.0 to 4.0.6 allows denial of service via packet injection or crafted capture file

References

Community reviews

Loading reviews…