Application hang via malformed RFC 7468 file
Published Dec 30, 2021 · Updated Nov 3, 2025
Infinite loop in Wireshark 3.6.0 and 3.4.0 through 3.4.10 allows attackers to cause an application hang via a malformed trace file. The RFC 7468 file parser repeatedly processes incomplete armored input instead of rejecting it as malformed, leaving its parsing loop unable to terminate. Exploitation requires the malformed trace to be opened or attacker-injected traffic to be processed, causing excessive CPU consumption and a sustained application hang.
Summary
What happened
Infinite loop in Wireshark 3.6.0 and 3.4.0 through 3.4.10 allows attackers to cause an application hang via a malformed trace file. The RFC 7468 file parser repeatedly processes incomplete armored input instead of rejecting it as malformed, leaving its parsing loop unable to terminate. Exploitation requires the malformed trace to be opened or attacker-injected traffic to be processed, causing excessive CPU consumption and a sustained application hang.
The record
- CVE
- CVE-2021-4182
- Published
- Dec 30, 2021
- Updated
- Nov 3, 2025
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- CWE-835, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 30, 2021CVE 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.4.0, <3.4.10
- Affected versionversion==3.6.0
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
- Incomplete RFC 7468 test.crt reproduction fileproof 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