# CVE-2025-9385: appneta tcpreplay tcprewrite edit_packet.c fix_ipv6_checksums use after free

> A local attacker can exploit a use-after-free flaw in tcprewrite to potentially execute arbitrary code or cause a denial of service.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Aug 2025
- **Updated:** 25 Aug 2025
- **Also known as:** DEBIAN-CVE-2025-9385, GHSA-h762-gwwm-v9vj, UBUNTU-CVE-2025-9385

## What is CVE-2025-9385?

CVE-2025-9385 is a medium-severity use after free vulnerability in Broadcom Tcpreplay, published on 24 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw has been found in appneta tcpreplay up to 4.5.1. The affected element is the function fix_ipv6_checksums of the file edit_packet.c of the component tcprewrite. This manipulation causes use after free. The attack is restricted to local execution. The exploit has been published and may be used. Upgrading to version 4.5.2-beta3 is sufficient to fix this issue. It is advisable to upgrade the affected component.

Weakness: CWE-416 (Use After Free), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2025-9385?

It affects 1 product.


Products: Broadcom Tcpreplay.

## How do I fix CVE-2025-9385?

Upgrade to a fixed version.

## Is CVE-2025-9385 being exploited?

There is no known exploitation of CVE-2025-9385 in the wild and no public exploit code.

## Other vulnerabilities in Broadcom Tcpreplay

- [CVE-2018-18408](https://insights.sbomify.com/CVE-2018-18408/): Use after free in n/a (critical 9.8)
- [CVE-2020-12740](https://insights.sbomify.com/CVE-2020-12740/): Memory corruption in n/a (critical 9.1)
- [CVE-2025-51006](https://insights.sbomify.com/CVE-2025-51006/): Use after free in n/a (high 7.8)
- [CVE-2022-37047](https://insights.sbomify.com/CVE-2022-37047/): Memory corruption in n/a (high 7.8)
- [CVE-2022-37048](https://insights.sbomify.com/CVE-2022-37048/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-9385 and fix it if it is affected.

What it is: CVE-2025-9385 is a medium-severity use after free vulnerability in Broadcom Tcpreplay, published on 24 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-9385 in the wild and no public exploit code.

Affected product: Broadcom Tcpreplay. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-9385/ (Markdown: https://insights.sbomify.com/CVE-2025-9385/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-9385
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-9385
- OSV: https://osv.dev/vulnerability/CVE-2025-9385

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-9385/
Summaries are generated and may contain mistakes; the official description above is the record.
