Local crash via stale reallocated packet pointer
Published Aug 19, 2025 · Updated Aug 19, 2025
Use-after-free in Tcpreplay tcprewrite 4.5.2-beta1 through 4.5.2-beta2 allows local users to crash the utility via a crafted pcap. With --fixlen padding enabled, untrunc_packet reallocates the packet buffer but leaves callers using the freed pointer during IPv4 checksum recalculation. A local user must cause tcprewrite to process the malformed capture; the demonstrated consequence is a SIGABRT process crash.
Summary
What happened
Use-after-free in Tcpreplay tcprewrite 4.5.2-beta1 through 4.5.2-beta2 allows local users to crash the utility via a crafted pcap. With --fixlen padding enabled, untrunc_packet reallocates the packet buffer but leaves callers using the freed pointer during IPv4 checksum recalculation. A local user must cause tcprewrite to process the malformed capture; the demonstrated consequence is a SIGABRT process crash.
The record
- CVE
- CVE-2025-9157
- Published
- Aug 19, 2025
- Updated
- Aug 19, 2025
- Vendor
- AppNeta
- Product
- Tcpreplay
- Classifications
- CWE-416, CWE-119
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 19, 2025CVE publishedPublication date reported by the CVE source.
- Aug 19, 2025Record 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=4.5.2-beta1
- Affected versionversion=4.5.2-beta2
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.
Weakness, pattern, technique
Public exploit references
- POC_tcprewrite_ipv4_checksums_use_after_free_69proof 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