CVE-2025-9386
BaseFortify
Publication date: 2025-08-24
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| broadcom | tcpreplay | to 4.5.1 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-119 | The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data. |
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-9386 is a use-after-free vulnerability in the AppNeta tcpreplay tool, specifically in the get_l2len_protocol function of the tcprewrite component. This flaw occurs when the function accesses memory that has already been freed after a packet buffer is resized, leading to referencing invalid memory. This can cause program crashes, unexpected behavior, or potentially arbitrary code execution. The attack requires local access and is exploitable with publicly available proof-of-concept code. Upgrading to version 4.5.2-beta3 fixes the issue. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by causing crashes or unexpected behavior in the tcpreplay tool, potentially leading to denial of service or arbitrary code execution on the affected system. It affects the confidentiality, integrity, and availability of the system where tcpreplay is used. Since the exploit requires local access, an attacker with limited privileges could exploit this to escalate impact. The vulnerability has moderate severity and is exploitable with publicly available proof-of-concept code. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by reproducing the use-after-free condition using a proof-of-concept malformed packet capture file named POC_tcprewrite_protocol_length_use_after_free_360. To detect it, compile tcprewrite with AddressSanitizer enabled and run the following command: tcprewrite --fixlen pad -i POC_tcprewrite_protocol_length_use_after_free_360 -o /dev/null. If the program crashes with a heap use-after-free error in get_l2len_protocol, the vulnerability is present. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to upgrade the affected tcpreplay component to version 4.5.2-beta3 or later, which resolves the use-after-free vulnerability in the get_l2len_protocol function. [1]