# CVE-2024-47600: GHSL-2024-248: GStreamer has an OOB-read in format_channel_mask

> An out-of-bounds read in GStreamer's format_channel_mask function allows attackers to read unintended stack memory and potentially cause undefined behavior.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/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-47600, AZL-54294, AZL-54359, AZL-62396, BELL-CVE-2024-47600, CLSA-2025-1747998930, DEBIAN-CVE-2024-47600, UBUNTU-CVE-2024-47600

## What is CVE-2024-47600?

CVE-2024-47600 is a medium-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-read vulnerability has been detected in the format_channel_mask function in gst-discoverer.c. The vulnerability affects the local array position, which is defined with a fixed size of 64 elements. However, the function gst_discoverer_audio_info_get_channels may return a guint channels value greater than 64. This causes the for loop to attempt access beyond the bounds of the position array, resulting in an OOB-read when an index greater than 63 is used. This vulnerability can result in reading unintended bytes from the stack. Additionally, the dereference of value->value_nick after the OOB-read can lead to further memory corruption or undefined behavior. This vulnerability is fixed in 1.24.10.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Gstreamer Gstreamer.

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

Upgrade to a fixed version.

## Is CVE-2024-47600 being exploited?

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

What it is: CVE-2024-47600 is a medium-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-47600 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-47600/ (Markdown: https://insights.sbomify.com/CVE-2024-47600/index.md)
```

## Sources

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

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