# CVE-2025-9157: appneta tcpreplay tcprewrite edit_packet.c untrunc_packet use after free

> A use-after-free vulnerability in tcprewrite allows local attackers 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:** 19 Aug 2025
- **Updated:** 19 Aug 2025
- **Also known as:** DEBIAN-CVE-2025-9157, GHSA-9v49-c9x8-3hm2, UBUNTU-CVE-2025-9157

## What is CVE-2025-9157?

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

### Official description

A vulnerability was determined in appneta tcpreplay up to 4.5.2-beta2. The impacted element is the function untrunc_packet of the file src/tcpedit/edit_packet.c of the component tcprewrite. Executing manipulation can lead to use after free. It is possible to launch the attack on the local host. The exploit has been publicly disclosed and may be utilized. This patch is called 73008f261f1cdf7a1087dc8759115242696d35da. Applying a patch is advised to resolve this issue.

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-9157?


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

Apply the vendor's patch.

## Is CVE-2025-9157 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-9157 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9157 is a medium-severity use after free vulnerability in appneta tcpreplay, published on 19 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-9157 exists.

Affected product: appneta 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-9157/ (Markdown: https://insights.sbomify.com/CVE-2025-9157/index.md)
```

## Sources

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

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