Skip to main content
CVE-2024-4854VulnerabilityPublished Updated

CVE-2024-4854: Wireshark · Infinite Loop

Affects WiresharkSource CVE Database V5

0

Not known to be exploited · CVSS 6.4 Medium.

Data as of 26 Oct 2026, 06:26 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 May 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
  • =3.6.0
  • =4.0.0
  • =4.2.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-4854, organizations should: 1) Monitor Wireshark Foundation announcements and promptly apply patches or updates once they become available for affected versions. 2) Avoid opening capture files from untrusted or unknown sources, especially those received via email or downloaded from the internet. 3) Implement network segmentation and filtering to limit exposure to potentially malicious packets targeting Wireshark dissectors. 4) Use sandboxing or isolated environments when analyzing suspicious capture files to contain potential hangs or crashes. 5) Educate security analysts and network engineers about the risk of crafted capture files and encourage verification of file provenance before analysis. 6) Consider alternative or updated network analysis tools temporarily if patching is delayed. 7) Employ automated monitoring to detect Wireshark process hangs or crashes to enable rapid recovery and investigation. These steps go beyond generic advice by focusing on operational controls and user awareness specific to this vulnerability's exploitation vectors.

Description

MONGO and ZigBee TLV dissector infinite loops in Wireshark 4.2.0 to 4.2.4, 4.0.0 to 4.0.14, and 3.6.0 to 3.6.22 allow denial of service via packet injection or crafted capture file

References

Community reviews

Loading reviews…