Process crash via freed pcap handle reuse
Published Jan 5, 2022 · Updated Aug 4, 2024
Use-after-free in tcpslice before 1.5 allows context-dependent attackers to crash the process through a crafted packet-capture file. In extract_slice(), the input-filtering loop can close the first pcap handle before pcap_dump_open() reuses that freed handle to obtain the output link-layer type. A user must invoke output writing on a crafted capture whose first input fails the slice condition; only a process crash is confirmed.
Summary
What happened
Use-after-free in tcpslice before 1.5 allows context-dependent attackers to crash the process through a crafted packet-capture file. In extract_slice(), the input-filtering loop can close the first pcap handle before pcap_dump_open() reuses that freed handle to obtain the output link-layer type. A user must invoke output writing on a crafted capture whose first input fails the slice condition; only a process crash is confirmed.
The record
- CVE
- CVE-2021-41043
- Published
- Jan 5, 2022
- Updated
- Aug 4, 2024
- Vendor
- The Tcpdump Group
- Product
- tcpslice
- Classifications
- CWE-416, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 5, 2022CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <1.5
What conditions does exploitation require?
What is affected?
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.
Public exploit references
- heap.pcap.zip crash proof of conceptproof 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