# CVE-2024-47544: GHSL-2024-238: GStreamer has NULL-pointer dereferences in MP4/MOV demuxer CENC handling

> A null pointer dereference in the GStreamer MP4/MOV demuxer allows attackers to cause a denial of service via crafted media files.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 Dec 2024
- **Updated:** 3 Nov 2025
- **Also known as:** AZL-62411, BIT-java-2024-47544, BIT-java-min-2024-47544, BIT-jre-2024-47544, CLSA-2025-1749506165, DEBIAN-CVE-2024-47544, MINI-rr4f-6pg2-5hqr, UBUNTU-CVE-2024-47544

## What is CVE-2024-47544?

CVE-2024-47544 is a medium-severity vulnerability in Gstreamer Gstreamer, published on 11 Dec 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

GStreamer is a library for constructing graphs of media-handling components. The function qtdemux_parse_sbgp in qtdemux.c is affected by a null dereference vulnerability. This vulnerability is fixed in 1.24.10.

Weakness: CWE-476 (NULL Pointer Dereference)

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

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-47544?

Upgrade java to a fixed version for your release line: 1.8.0 or 8.0.451.

## Is CVE-2024-47544 being exploited?

There is no known exploitation of CVE-2024-47544 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-47544 and fix it if it is affected.

What it is: CVE-2024-47544 is a medium-severity vulnerability in Gstreamer Gstreamer, published on 11 Dec 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-47544 in the wild and no public exploit code.

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

## Sources

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

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