# CVE-2024-3024: appneta tcpreplay get.c get_layer4_v6 heap-based overflow

> Local attackers can trigger a heap-based buffer overflow in tcpreplay, potentially leading to code execution or denial of service.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 28 Mar 2024
- **Updated:** 1 Aug 2024
- **Also known as:** DEBIAN-CVE-2024-3024, GHSA-phrr-qc3r-4v9p, MGASA-2024-0305

## What is CVE-2024-3024?

CVE-2024-3024 is a medium-severity memory corruption vulnerability in Broadcom Tcpreplay, published on 28 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in appneta tcpreplay up to 4.4.4. It has been classified as problematic. This affects the function get_layer4_v6 of the file /tcpreplay/src/common/get.c. The manipulation leads to heap-based buffer overflow. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used. The identifier VDB-258333 was assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-787 (Out-of-bounds Write), CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2024-3024?

It affects 1 product.


Products: Broadcom Tcpreplay.

## How do I fix CVE-2024-3024?

No fix published yet.

## Is CVE-2024-3024 being exploited?

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

## 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-2024-3024 and fix it if it is affected.

What it is: CVE-2024-3024 is a medium-severity memory corruption vulnerability in Broadcom Tcpreplay, published on 28 Mar 2024. 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-2024-3024 exists.

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-2024-3024/ (Markdown: https://insights.sbomify.com/CVE-2024-3024/index.md)
```

## Sources

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

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