# CVE-2024-47537: GHSL-2024-094: GStreamer has an OOB-write in isomp4/qtdemux.c

> An integer overflow in GStreamer's MP4 demuxer allows out-of-bounds writes, potentially enabling remote code execution via malicious media files.

- **Severity:** High 8.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Dec 2024
- **Updated:** 3 Nov 2025
- **Also known as:** AZL-62417, CLSA-2025-1764688338, DEBIAN-CVE-2024-47537, UBUNTU-CVE-2024-47537

## What is CVE-2024-47537?

CVE-2024-47537 is a high-severity vulnerability in Gstreamer Gstreamer, published on 11 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

GStreamer is a library for constructing graphs of media-handling components. The program attempts to reallocate the memory pointed to by stream->samples to accommodate stream->n_samples + samples_count elements of type QtDemuxSample. The problem is that samples_count is read from the input file. And if this value is big enough, this can lead to an integer overflow during the addition. As a consequence, g_try_renew might allocate memory for a significantly smaller number of elements than intended. Following this, the program iterates through samples_count elements and attempts to write samples_count number of elements, potentially exceeding the actual allocated memory size and causing an OOB-write. This vulnerability is fixed in 1.24.10.

Weakness: CWE-787 (Out-of-bounds Write), CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Gstreamer Gstreamer.

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

Upgrade to a fixed version.

## Is CVE-2024-47537 being exploited?

There is no known exploitation of CVE-2024-47537 in the wild and no public exploit code.

## Other vulnerabilities in Gstreamer Gstreamer

- [CVE-2026-3083](https://insights.sbomify.com/CVE-2026-3083/): GStreamer rtpqdm2depay Out-Of-Bounds Write Remote Code Execution Vulnerability (high 8.8)
- [CVE-2026-3085](https://insights.sbomify.com/CVE-2026-3085/): GStreamer rtpqdm2depay Heap-based Buffer Overflow Remote Code Execution Vulnerability (high 8.8)
- [CVE-2023-37328](https://insights.sbomify.com/CVE-2023-37328/): GStreamer PGS File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability (high 8.8)
- [CVE-2023-37329](https://insights.sbomify.com/CVE-2023-37329/): GStreamer SRT File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability (high 8.8)
- [CVE-2023-38103](https://insights.sbomify.com/CVE-2023-38103/): GStreamer RealMedia File Parsing Integer Overflow Remote Code Execution Vulnerability (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-47537 is a high-severity vulnerability in Gstreamer Gstreamer, published on 11 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-47537 in the wild and no public exploit code.

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

## Sources

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

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