Local process crash via double-free cleanup
Published Dec 21, 2023 · Updated Feb 13, 2025
Double free in tcprewrite 4.4.3 and 4.4.4 allows local users to crash the process by opening a crafted Juniper Ethernet capture. During shutdown, dlt_jnpr_ether_cleanup recursively frees encoder configuration already freed and nulled by dlt_en10mb_cleanup. Execution requires a user to run tcprewrite on the crafted file; the documented consequence is an abort, not data disclosure or modification.
Summary
What happened
Double free in tcprewrite 4.4.3 and 4.4.4 allows local users to crash the process by opening a crafted Juniper Ethernet capture. During shutdown, dlt_jnpr_ether_cleanup recursively frees encoder configuration already freed and nulled by dlt_en10mb_cleanup. Execution requires a user to run tcprewrite on the crafted file; the documented consequence is an abort, not data disclosure or modification.
The record
- CVE
- CVE-2023-4256
- Published
- Dec 21, 2023
- Updated
- Feb 13, 2025
- Vendor
- Fedora Project
- Product
- Fedora Linux
- Classifications
- CWE-415, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 21, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
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
- Upstream tcprewrite crafted-capture 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