Denial of service via DOCSIS dissector loop
Published Jan 3, 2024 · Updated Mar 27, 2026
Infinite loop in the DOCSIS dissector in Wireshark 4.2.0 allows attackers to crash the application via malformed packet input. Extended-header parsing repeatedly adds the same docsis.ehdr.type field to the protocol tree until the million-item loop guard aborts dissection. Triggering requires an injected malformed packet to be captured or a crafted trace file to be opened, and the documented consequence is application interruption.
Summary
What happened
Infinite loop in the DOCSIS dissector in Wireshark 4.2.0 allows attackers to crash the application via malformed packet input. Extended-header parsing repeatedly adds the same docsis.ehdr.type field to the protocol tree until the million-item loop guard aborts dissection. Triggering requires an injected malformed packet to be captured or a crafted trace file to be opened, and the documented consequence is application interruption.
The record
- CVE
- CVE-2024-0211
- Published
- Jan 3, 2024
- Updated
- Mar 27, 2026
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- CWE-835, T1499.004
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 3, 2024CVE publishedPublication date reported by the CVE source.
- Mar 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.2.0 <4.2.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- fuzz-2024-01-01-7166.pcapproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo