Application crash via unchecked TIPC dissector recursion
Published Jan 24, 2023 · Updated Nov 3, 2025
Uncontrolled recursion in Wireshark 3.6.0 through 3.6.10 and 4.0.0 through 4.0.2 allows attackers to crash the application. The TIPC internal-protocol parser repeatedly calls the main TIPC dissector on nested packet data without enforcing a recursion-depth limit, exhausting the call stack. A malformed live packet must reach an active capture, or a user must open the crafted trace; either path terminates Wireshark or TShark.
Summary
What happened
Uncontrolled recursion in Wireshark 3.6.0 through 3.6.10 and 4.0.0 through 4.0.2 allows attackers to crash the application. The TIPC internal-protocol parser repeatedly calls the main TIPC dissector on nested packet data without enforcing a recursion-depth limit, exhausting the call stack. A malformed live packet must reach an active capture, or a user must open the crafted trace; either path terminates Wireshark or TShark.
The record
- CVE
- CVE-2023-0412
- Published
- Jan 24, 2023
- Updated
- Nov 3, 2025
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- CWE-404, T1204.002, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 24, 2023CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record 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=>=3.6.0, <3.6.11
- Affected versionversion=>=4.0.0, <4.0.3
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-2022-12-30-11007.pcap 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