# CVE-2023-29578: Memory corruption in n/a

> A heap buffer overflow in the MP4StringProperty destructor allows attackers to execute arbitrary code or cause denial of service via crafted MP4 files.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Apr 2023
- **Updated:** 4 Feb 2025
- **Also known as:** GHSA-qjvw-vhjr-4r9r, UBUNTU-CVE-2023-29578

## What is CVE-2023-29578?

CVE-2023-29578 is a high-severity memory corruption vulnerability in n/a, published on 24 Apr 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

mp4v2 v2.0.0 was discovered to contain a heap buffer overflow via the mp4v2::impl::MP4StringProperty::~MP4StringProperty() function at src/mp4property.cpp.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2023-29578?

It affects 1 product.


Products: Mp4v2 Project Mp4v2.

## How do I fix CVE-2023-29578?

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

## Is CVE-2023-29578 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-33718](https://insights.sbomify.com/CVE-2023-33718/): Memory corruption in n/a (high 8.8)
- [CVE-2023-29584](https://insights.sbomify.com/CVE-2023-29584/): Memory corruption in n/a (high 8.8)
- [CVE-2018-7339](https://insights.sbomify.com/CVE-2018-7339/): Integer overflow in n/a (high 8.8)
- [CVE-2023-33720](https://insights.sbomify.com/CVE-2023-33720/): Denial of service in n/a (medium 6.5)
- [CVE-2018-17235](https://insights.sbomify.com/CVE-2018-17235/): Memory corruption in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-29578 and fix it if it is affected.

What it is: CVE-2023-29578 is a high-severity memory corruption vulnerability in n/a, published on 24 Apr 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-29578 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-2023-29578/ (Markdown: https://insights.sbomify.com/CVE-2023-29578/index.md)
```

## Sources

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

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