# CVE-2024-47776: GHSL-2024-260: GStreamer has a OOB-read in gst_wavparse_cue_chunk > An out-of-bounds read in GStreamer's WAV parser allows attackers to cause crashes or leak sensitive data via crafted media files. - **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:** AZL-62372, BIT-java-2024-47776, BIT-java-min-2024-47776, BIT-jre-2024-47776, DEBIAN-CVE-2024-47776, MINI-cxqc-rxhf-pv9v, UBUNTU-CVE-2024-47776 ## What is CVE-2024-47776? CVE-2024-47776 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 has been discovered in gst_wavparse_cue_chunk within gstwavparse.c. The vulnerability happens due to a discrepancy between the size of the data buffer and the size value provided to the function. This mismatch causes the comparison if (size < 4 + ncues * 24) to fail in some cases, allowing the subsequent loop to access beyond the bounds of the data buffer. The root cause of this discrepancy stems from a miscalculation when clipping the chunk size based on upstream data size. This vulnerability allows reading beyond the bounds of the data buffer, potentially leading to a crash (denial of service) or the leak of sensitive data. This vulnerability is fixed in 1.24.10. Weakness: CWE-125 (Out-of-bounds Read) ## Which versions are affected by CVE-2024-47776? 3 open source packages ship an affected version, including java, java-min and jre. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `java` | Bitnami | All versions | 1.8.0, 8.0.451 | | `java-min` | Bitnami | All versions | 1.8.0, 8.0.451 | | `jre` | Bitnami | All versions | 1.8.0, 8.0.451 | Products: Gstreamer Gstreamer. ## How do I fix CVE-2024-47776? Upgrade java to a fixed version for your release line: 1.8.0 or 8.0.451. ## Is CVE-2024-47776 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47776 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-47776 and fix it if it is affected. What it is: CVE-2024-47776 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-47776 exists. Affected packages and fixed versions: - java (Bitnami): affected all versions; fixed in 1.8.0, 8.0.451 - java-min (Bitnami): affected all versions; fixed in 1.8.0, 8.0.451 - jre (Bitnami): affected all versions; fixed in 1.8.0, 8.0.451 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-47776/ (Markdown: https://insights.sbomify.com/CVE-2024-47776/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-47776 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-47776 - OSV: https://osv.dev/vulnerability/CVE-2024-47776 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-47776/ Summaries are generated and may contain mistakes; the official description above is the record.