# CVE-2024-57510: Memory corruption in n/a

> A local attacker can execute arbitrary code via a buffer overflow in the Bento4 media library's memory stream handling.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** No
- **Published:** 29 Jan 2025
- **Updated:** 3 Feb 2025
- **Also known as:** GHSA-cj9r-cvpx-fx3h

## What is CVE-2024-57510?

CVE-2024-57510 is a high-severity memory corruption vulnerability in n/a, published on 29 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer Overflow vulnerability in Bento4 mp42avc v.3bdc891602d19789b8e8626e4a3e613a937b4d35 allows a local attacker to execute arbitrary code via the AP4_MemoryByteStream::WritePartial.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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


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

No fix has been published for CVE-2024-57510 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-57510 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-57510 and fix it if it is affected.

What it is: CVE-2024-57510 is a high-severity memory corruption vulnerability in n/a, published on 29 Jan 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-2024-57510 exists.

Affected product: n/a. 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-57510/ (Markdown: https://insights.sbomify.com/CVE-2024-57510/index.md)
```

## Sources

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

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