Application crash via malformed packet dissection
Published Jan 24, 2023 · Updated Nov 3, 2025
Dissection engine flaws in Wireshark 3.6.0 through 3.6.10 and 4.0.0 through 4.0.2 allow remote attackers to crash the application. A bug in the conversation tracking module causes some dissectors to crash, but the precise faulty operation is not public. Reachability requires injecting a malformed packet onto a monitored network or persuading a user to open a malformed capture file, and the reported consequence is a process crash.
Summary
What happened
Dissection engine flaws in Wireshark 3.6.0 through 3.6.10 and 4.0.0 through 4.0.2 allow remote attackers to crash the application. A bug in the conversation tracking module causes some dissectors to crash, but the precise faulty operation is not public. Reachability requires injecting a malformed packet onto a monitored network or persuading a user to open a malformed capture file, and the reported consequence is a process crash.
The record
- CVE
- CVE-2023-0413
- Published
- Jan 24, 2023
- Updated
- Nov 3, 2025
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- CWE-404, T1499.004
- 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
No public exploit references are available in this record.
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