Process crash via malformed IPv6 capture
Published Aug 18, 2022 · Updated Aug 3, 2024
Heap-based buffer overflow in Tcpreplay 4.4.1 allows context-dependent attackers to crash tcprewrite via a crafted packet capture. The get_ipv6_next function reads four bytes beyond its heap allocation while traversing malformed IPv6 extension data without an adequate end-pointer check. Exploitation requires local processing of an untrusted capture, and the demonstrated consequence is tcprewrite process termination.
Summary
What happened
Heap-based buffer overflow in Tcpreplay 4.4.1 allows context-dependent attackers to crash tcprewrite via a crafted packet capture. The get_ipv6_next function reads four bytes beyond its heap allocation while traversing malformed IPv6 extension data without an adequate end-pointer check. Exploitation requires local processing of an untrusted capture, and the demonstrated consequence is tcprewrite process termination.
The record
- CVE
- CVE-2022-37047
- Published
- Aug 18, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 18, 2022CVE 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Public exploit references
- POC2.zip tcprewrite reproducerproof 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