Denial of service via USB HID memory leak
Published Feb 17, 2021 · Updated Aug 3, 2024
A memory leak in the USB HID dissector in Wireshark 3.4.0 through 3.4.2 allows attackers to exhaust resources via malformed input. The USB HID decoding path uses mismatched g_strdup() and g_free() allocation handling; the fix moves formatted strings into packet-scoped memory. Reachability requires injection of a malformed packet onto a monitored network or interaction that causes a crafted capture file to be opened, resulting in excessive resource consumption.
Summary
What happened
A memory leak in the USB HID dissector in Wireshark 3.4.0 through 3.4.2 allows attackers to exhaust resources via malformed input. The USB HID decoding path uses mismatched g_strdup() and g_free() allocation handling; the fix moves formatted strings into packet-scoped memory. Reachability requires injection of a malformed packet onto a monitored network or interaction that causes a crafted capture file to be opened, resulting in excessive resource consumption.
The record
- CVE
- CVE-2021-22173
- Published
- Feb 17, 2021
- Updated
- Aug 3, 2024
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- CWE-401, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 17, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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.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
- Wireshark fuzz capture for issue 17124proof 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