Application crash via recursive CBOR byte-string parsing
Published Aug 24, 2023 · Updated Mar 27, 2026
Uncontrolled recursion in Wireshark 4.0.0 through 4.0.7 allows attackers to crash the application through malformed CBOR input. The dissect_cbor_byte_string() and dissect_cbor_text_string() paths recursively process nested indefinite-length strings without a depth limit until the stack overflows. A malformed injected packet or crafted capture file must be dissected, after which resource exhaustion or stack overflow terminates Wireshark or TShark.
Summary
What happened
Uncontrolled recursion in Wireshark 4.0.0 through 4.0.7 allows attackers to crash the application through malformed CBOR input. The dissect_cbor_byte_string() and dissect_cbor_text_string() paths recursively process nested indefinite-length strings without a depth limit until the stack overflows. A malformed injected packet or crafted capture file must be dissected, after which resource exhaustion or stack overflow terminates Wireshark or TShark.
The record
- CVE
- CVE-2023-4512
- Published
- Aug 24, 2023
- Updated
- Mar 27, 2026
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- CWE-674, T1499.004
- Attack vector
- Unavailable
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 24, 2023CVE 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.0.0 <4.0.8
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
- CBOR recursive byte-string crash reproducerproof 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