CVE-2024-4854: Wireshark · Infinite Loop
Affects WiresharkSource CVE Database V5
Not known to be exploited · CVSS 6.4 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- 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:HExploitation evidence
Disclosed: evidence found.
CVE published 14 May 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
GitHubwireshark/wiresharkpkg:github/wireshark/wiresharkOther threats | Affected
| 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
- wireshark.org/security/wnpa-sec-2024-07.html (opens in a new tab)
- gitlab.com/wireshark/wireshark/-/issues/19726 (opens in a new tab)
- gitlab.com/wireshark/wireshark/-/merge_requests/15047 (opens in a new tab)
- gitlab.com/wireshark/wireshark/-/merge_requests/15499 (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/66H2BSENPSIALF2WIZF7M3QBVWYBMFGW/ (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7MKFJAZDKXGFFQPRDYLX2AANRNMYZZEZ/ (opens in a new tab)
- lists.debian.org/debian-lts-announce/2024/09/msg00049.html (opens in a new tab)