# CVE-2024-6063: GPAC MP4Box dmx_m2ts.c m2tsdmx_on_event null pointer dereference

> A local attacker can cause a denial of service via null pointer dereference in GPAC MP4Box, requiring a patch for mitigation.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **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:** 17 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** DEBIAN-CVE-2024-6063, GHSA-xh4q-h4wh-8q8p, UBUNTU-CVE-2024-6063

## What is CVE-2024-6063?

CVE-2024-6063 is a medium-severity vulnerability in Gpac Gpac, published on 17 Jun 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 GPAC 2.5-DEV-rev228-g11067ea92-master. It has been classified as problematic. This affects the function m2tsdmx_on_event of the file src/filters/dmx_m2ts.c of the component MP4Box. The manipulation leads to null pointer dereference. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. The patch is named 8767ed0a77c4b02287db3723e92c2169f67c85d5. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-268791.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Gpac Gpac.

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

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

## Is CVE-2024-6063 being exploited?

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

## Other vulnerabilities in Gpac Gpac

- [CVE-2023-46427](https://insights.sbomify.com/CVE-2023-46427/): Null dereference in n/a (critical 9.8)
- [CVE-2023-46932](https://insights.sbomify.com/CVE-2023-46932/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-36190](https://insights.sbomify.com/CVE-2022-36190/): Use after free in n/a (critical 9.8)
- [CVE-2021-28300](https://insights.sbomify.com/CVE-2021-28300/): Null dereference in n/a (critical 9.8)
- [CVE-2020-11558](https://insights.sbomify.com/CVE-2020-11558/): Use after free in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-6063 is a medium-severity vulnerability in Gpac Gpac, published on 17 Jun 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-6063 exists.

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

## Sources

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

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