Analysis interruption via nonadvancing Kafka tagged-field loop
Published Jan 11, 2023 · Updated Nov 3, 2025
Memory exhaustion in Wireshark 3.6.0 through 3.6.9 and 4.0.0 through 4.0.1 allows attackers to interrupt analysis via Kafka packets. The dissect_kafka_array_elements loop trusts a huge varint count while failed field decodes consume zero bytes, so the read offset never advances. A malformed packet must be injected into captured traffic or opened as a capture file, causing sustained CPU and memory consumption that denies packet analysis.
Summary
What happened
Memory exhaustion in Wireshark 3.6.0 through 3.6.9 and 4.0.0 through 4.0.1 allows attackers to interrupt analysis via Kafka packets. The dissect_kafka_array_elements loop trusts a huge varint count while failed field decodes consume zero bytes, so the read offset never advances. A malformed packet must be injected into captured traffic or opened as a capture file, causing sustained CPU and memory consumption that denies packet analysis.
The record
- CVE
- CVE-2022-4344
- Published
- Jan 11, 2023
- Updated
- Nov 3, 2025
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 11, 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.10
- Affected versionversion=>=4.0.0, <4.0.2
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
- Kafka tagged-fields proof-of-concept capturesproof 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