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

> A memory leak in GPAC allows attackers to cause denial of service by exhausting system memory.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Feb 2024
- **Updated:** 9 May 2025
- **Also known as:** DEBIAN-CVE-2024-24265, GHSA-2qm8-4j25-v4w6, UBUNTU-CVE-2024-24265

## What is CVE-2024-24265?

CVE-2024-24265 is a high-severity memory corruption vulnerability in Gpac Gpac, published on 5 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

gpac v2.2.1 was discovered to contain a memory leak via the dst_props variable in the gf_filter_pid_merge_properties_internal function.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

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

It affects 1 product.


Products: Gpac Gpac.

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

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

## Is CVE-2024-24265 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-24265 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-24265 and fix it if it is affected.

What it is: CVE-2024-24265 is a high-severity memory corruption vulnerability in Gpac Gpac, published on 5 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-24265 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-24265/ (Markdown: https://insights.sbomify.com/CVE-2024-24265/index.md)
```

## Sources

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

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