Crash via unchecked packet header lengths
Published Apr 12, 2022 · Updated Aug 3, 2024
Heap-based buffer overflow in Tcpreplay 4.4.1 allows local users to crash tcpreplay-edit by processing a crafted packet capture. The checksum path trusts corrupt IPv4 header lengths, causing do_checksum_math to read two-byte words beyond the heap-allocated packet buffer. The user must invoke packet editing on the crafted capture; the demonstrated consequence is an AddressSanitizer-detected abort, not code execution.
Summary
What happened
Heap-based buffer overflow in Tcpreplay 4.4.1 allows local users to crash tcpreplay-edit by processing a crafted packet capture. The checksum path trusts corrupt IPv4 header lengths, causing do_checksum_math to read two-byte words beyond the heap-allocated packet buffer. The user must invoke packet editing on the crafted capture; the demonstrated consequence is an AddressSanitizer-detected abort, not code execution.
The record
- CVE
- CVE-2022-27418
- Published
- Apr 12, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 12, 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.
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 crafted packet captureproof 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