Process crash via freed Snappy buffer read
Published Jul 14, 2023 · Updated Nov 3, 2025
Heap use-after-free in the Kafka dissector in Wireshark 3.6.0 through 3.6.14 and 4.0.0 through 4.0.6 allows attackers to crash the process. decompress_snappy frees the decompressed buffer while a TVB still references it, and dissect_kafka_record then reads a variable-length integer from that freed storage. Processing an injected malformed packet or opening a crafted capture file triggers the crash, interrupting the analysis session.
Summary
What happened
Heap use-after-free in the Kafka dissector in Wireshark 3.6.0 through 3.6.14 and 4.0.0 through 4.0.6 allows attackers to crash the process. decompress_snappy frees the decompressed buffer while a TVB still references it, and dissect_kafka_record then reads a variable-length integer from that freed storage. Processing an injected malformed packet or opening a crafted capture file triggers the crash, interrupting the analysis session.
The record
- CVE
- CVE-2023-3648
- Published
- Jul 14, 2023
- Updated
- Nov 3, 2025
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- CWE-762, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 14, 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.15
- Affected versionversion=4.0.0 <4.0.7
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-2023-05-26-6880.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