CLI crash via recursive Juniper DLT cleanup
Published Apr 12, 2022 · Updated Aug 3, 2024
Double-free in Tcpreplay 4.4.1 allows local users to crash tcprewrite by processing a crafted packet capture through the Juniper DLT plugin. The dlt_jnpr_ether_cleanup function calls tcpedit_dlt_cleanup on the Juniper subcontext and then frees that same subcontext again. Triggering requires local users to run tcprewrite on the crafted capture; the demonstrated consequence is termination of the CLI process.
Summary
What happened
Double-free in Tcpreplay 4.4.1 allows local users to crash tcprewrite by processing a crafted packet capture through the Juniper DLT plugin. The dlt_jnpr_ether_cleanup function calls tcpedit_dlt_cleanup on the Juniper subcontext and then frees that same subcontext again. Triggering requires local users to run tcprewrite on the crafted capture; the demonstrated consequence is termination of the CLI process.
The record
- CVE
- CVE-2022-27416
- Published
- Apr 12, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415, T1204.002
- 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
- Tcprewrite Juniper DLT double-free 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