Denial of service via mismatched buffer deallocation
Published Jul 20, 2021 · Updated Aug 3, 2024
Invalid memory deallocation in Wireshark 3.2.0 through 3.2.14 and 3.4.0 through 3.4.6 allows attackers to crash it via DNP data. On the CRC-error path, dissect_dnp3_message calls g_free on al_buffer even though the buffer belongs to the packet-scope wmem pool. A malformed DNP packet injected into a live capture or opened from a crafted capture file terminates Wireshark or TShark.
Summary
What happened
Invalid memory deallocation in Wireshark 3.2.0 through 3.2.14 and 3.4.0 through 3.4.6 allows attackers to crash it via DNP data. On the CRC-error path, dissect_dnp3_message calls g_free on al_buffer even though the buffer belongs to the packet-scope wmem pool. A malformed DNP packet injected into a live capture or opened from a crafted capture file terminates Wireshark or TShark.
The record
- CVE
- CVE-2021-22235
- Published
- Jul 20, 2021
- Updated
- Aug 3, 2024
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- CWE-835, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 20, 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.2.0, <3.2.15
- Affected versionversion=>=3.4.0, <3.4.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-2021-06-26-9972.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