# CVE-2024-47615: GHSL-2024-117: GStreamer has an out-of-bounds write in Ogg demuxer

> An out-of-bounds write in the GStreamer Ogg demuxer allows attackers to corrupt memory and potentially execute code 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:** ALPINE-CVE-2024-47615, AZL-54309, AZL-54365, AZL-62405, BELL-CVE-2024-47615, CLSA-2025-1749505638, CLSA-2025-1763139214, CLSA-2025-1764325377, DEBIAN-CVE-2024-47615, UBUNTU-CVE-2024-47615

## What is CVE-2024-47615?

CVE-2024-47615 is a high-severity memory corruption 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. An OOB-Write has been detected in the function gst_parse_vorbis_setup_packet within vorbis_parse.c. The integer size is read from the input file without proper validation. As a result, size can exceed the fixed size of the pad->vorbis_mode_sizes array (which size is 256). When this happens, the for loop overwrites the entire pad structure with 0s and 1s, affecting adjacent memory as well. This OOB-write can overwrite up to 380 bytes of memory beyond the boundaries of the pad->vorbis_mode_sizes array. This vulnerability is fixed in 1.24.10.

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

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

It affects 1 product.


Products: Gstreamer Gstreamer.

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

Upgrade to a fixed version.

## Is CVE-2024-47615 being exploited?

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

## 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-47615 and fix it if it is affected.

What it is: CVE-2024-47615 is a high-severity memory corruption 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47615 exists.

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

## Sources

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

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