Skip to main content
CVE-2024-0209VulnerabilityPublished Updated

CVE-2024-0209: Wireshark · NULL Pointer Dereference

Affects WiresharkSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% 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:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Jan 2024

  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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
GitHubwireshark/wiresharkpkg:github/wireshark/wiresharkOther threatsAffected
  • =4.2.0
  • =4.0.0
  • =3.6.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

To mitigate CVE-2024-0209, organizations should: 1) Monitor Wireshark Foundation announcements and apply patches promptly once released for affected versions (3.6.x, 4.0.x, 4.2.0). 2) Avoid opening capture files from untrusted or unknown sources, especially those containing IEEE 1609.2 traffic. 3) Implement strict network segmentation and filtering to limit exposure to crafted packets that could trigger the vulnerability. 4) Use sandboxing or isolated environments when analyzing suspicious capture files to contain potential crashes. 5) Educate security analysts and network engineers about the risk of crafted packets and malicious capture files targeting Wireshark. 6) Consider alternative or updated protocol analyzers for IEEE 1609.2 traffic until patches are applied. 7) Employ intrusion detection systems to detect anomalous IEEE 1609.2 packets that could indicate exploitation attempts. These steps go beyond generic advice by focusing on operational controls around packet handling and analyst workflows.

Description

IEEE 1609.2 dissector crash in Wireshark 4.2.0, 4.0.0 to 4.0.11, and 3.6.0 to 3.6.19 allows denial of service via packet injection or crafted capture file

References

Community reviews

Loading reviews…