Skip to main content
VulnerabilityPublished Updated

CVE-2023-0413: Null Pointer Dereference in Wireshark

Affects WiresharkSource CVE Database V5

0

Not known to be exploited · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 17:16 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jan 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
  • >=3.6.0 <=3.6.10
  • >=4.0.0 <=4.0.2
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 immediately to versions 3.6.11 or 4.0.3 or later, where this vulnerability is fixed.
  2. Implement strict policies to validate and verify the source of capture files before opening them in Wireshark.
  3. Use sandboxing or isolated environments when analyzing untrusted capture files to contain potential crashes.
  4. Employ network segmentation and filtering to reduce exposure to malicious packet injection, especially on networks where Wireshark is used.
  5. Educate users on the risks of opening capture files from untrusted sources and enforce least privilege principles for users running Wireshark.
  6. Monitor Wireshark usage logs and system stability to detect abnormal crashes that may indicate exploitation attempts.
  7. Consider alternative or complementary network analysis tools with robust security controls for critical environments.

Description

Dissection engine bug in Wireshark 4.0.0 to 4.0.2 and 3.6.0 to 3.6.10 and allows denial of service via packet injection or crafted capture file

References

Community reviews

Loading reviews…