Resource exhaustion via untracked composite TVB buffers
Published Feb 27, 2020 · Updated Aug 4, 2024
LTE RRC memory leak in Wireshark 2.6.0 through 2.6.14, 3.0.0 through 3.0.8, and 3.2.0 through 3.2.1 allows attackers to exhaust resources. Three sites in the generated LTE RRC code append standalone real-data buffers to composite TVBs instead of child buffers tied to the input TVB, leaving their lifetimes untracked. A malformed packet injected onto a monitored network needs no authentication, while the capture-file path requires an operator to open the crafted trace; either path causes excessive CPU use and service interruption.
Summary
What happened
LTE RRC memory leak in Wireshark 2.6.0 through 2.6.14, 3.0.0 through 3.0.8, and 3.2.0 through 3.2.1 allows attackers to exhaust resources. Three sites in the generated LTE RRC code append standalone real-data buffers to composite TVBs instead of child buffers tied to the input TVB, leaving their lifetimes untracked. A malformed packet injected onto a monitored network needs no authentication, while the capture-file path requires an operator to open the crafted trace; either path causes excessive CPU use and service interruption.
The record
- CVE
- CVE-2020-9431
- Published
- Feb 27, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 27, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- ClusterFuzz fuzzshark LTE RRC reproducer testcaseproof 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