Local crash via truncated MPLS packet parsing
Published Mar 26, 2022 · Updated Aug 3, 2024
Heap buffer over-read in tcpprep in Broadcom Tcpreplay 4.4.1 allows local users to crash the process via a crafted PCAP file. The parse_mpls function in common/get.c advances through MPLS headers without ensuring that four bytes remain before dereferencing the next header. Exploitation requires a user to process the attacker-supplied capture with tcpprep; the demonstrated result is an out-of-bounds four-byte read and process abort, not code execution.
Summary
What happened
Heap buffer over-read in tcpprep in Broadcom Tcpreplay 4.4.1 allows local users to crash the process via a crafted PCAP file. The parse_mpls function in common/get.c advances through MPLS headers without ensuring that four bytes remain before dereferencing the next header. Exploitation requires a user to process the attacker-supplied capture with tcpprep; the demonstrated result is an out-of-bounds four-byte read and process abort, not code execution.
The record
- CVE
- CVE-2022-27942
- Published
- Mar 26, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 26, 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.zip tcpprep crash 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