CVE-2024-0210: Wireshark · Uncontrolled Recursion
Affects WiresharkSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Jan 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
1. Avoid opening capture files from untrusted or unknown sources, especially those containing Zigbee traffic. 2. Monitor and filter Zigbee network traffic to detect and block malformed or suspicious packets that could trigger the vulnerability. 3. Implement strict access controls on systems running Wireshark to limit exposure to crafted files. 4. Use sandboxing or isolated environments when analyzing untrusted capture files to contain potential crashes. 5. Stay alert for official patches or updates from the Wireshark Foundation and apply them promptly once available. 6. Educate network analysts and security teams about the risks of processing untrusted Zigbee data. 7. Consider alternative tools or updated versions of Wireshark that address this vulnerability for critical environments. 8. Employ network segmentation to isolate IoT and Zigbee traffic from critical monitoring infrastructure.
Description
Zigbee TLV dissector crash in Wireshark 4.2.0 allows denial of service via packet injection or crafted capture file