Crash via unchecked IPv6 extension-header read
Published May 8, 2020 · Updated Aug 4, 2024
Heap-based buffer over-read in Tcpreplay 4.3.2 and earlier allows attackers to crash tcprewrite via a crafted PCAP file. The get_ipv6_next function reads a four-byte value from exthdr plus len without first ensuring that the address remains inside the allocated packet buffer. The attacker-supplied file must be processed by tcprewrite; observed consequences are a crash and a heap read beyond packet data.
Summary
What happened
Heap-based buffer over-read in Tcpreplay 4.3.2 and earlier allows attackers to crash tcprewrite via a crafted PCAP file. The get_ipv6_next function reads a four-byte value from exthdr plus len without first ensuring that the address remains inside the allocated packet buffer. The attacker-supplied file must be processed by tcprewrite; observed consequences are a crash and a heap read beyond packet data.
The record
- CVE
- CVE-2020-12740
- Published
- May 8, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 8, 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.
Public exploit references
- Issue 576 malicious PCAP 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