Skip to main content
VulnerabilityPublished Updated

CVE-2023-2856: Buffer Over-read in Wireshark

Affects WiresharkSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.7% chance of exploitation in 30 days – higher than 78% 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 26 May 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
  • <=4.0.5
  • =3.6.0
  • <=3.6.13
Fixed in–
Ubuntuubuntu/wiresharkpkg:deb/ubuntu/wiresharkOther threatsAffected
  • =4.0.0
  • <=4.0.5
  • =3.6.0
  • <=3.6.13
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. Upgrade Wireshark to the latest available versions beyond 3.6.13 and 4.0.5, specifically 3.6.14 or 4.0.6 and later, as these contain fixes for this vulnerability.
  2. Implement strict policies to avoid opening capture files from untrusted or unknown sources.
  3. Use sandboxing or isolated environments when analyzing suspicious capture files to contain potential crashes.
  4. Educate network analysts and security teams about the risks of opening unverified capture files and encourage verification of file provenance.
  5. Monitor Wireshark usage logs and system stability to detect unusual crashes that may indicate exploitation attempts.
  6. Employ network segmentation and access controls to limit exposure of critical analysis systems to potentially malicious files.
  7. Stay informed through vendor advisories and security bulletins for any updates or patches related to this vulnerability.
  8. Consider alternative network analysis tools temporarily if patching is delayed and risk is high.

Description

VMS TCPIPtrace file parser crash in Wireshark 4.0.0 to 4.0.5 and 3.6.0 to 3.6.13 allows denial of service via crafted capture file

References

Community reviews

Loading reviews…