# CVE-2024-47613: GHSL-2024-118: GStreamer has a null pointer dereference in gst_gdk_pixbuf_dec_flush

> A null pointer dereference in GStreamer's gdk_pixbuf decoder allows attackers to cause a denial of service via crafted 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-62336, CLSA-2025-1749826187, CLSA-2025-1751141320, DEBIAN-CVE-2024-47613, UBUNTU-CVE-2024-47613

## What is CVE-2024-47613?

CVE-2024-47613 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. A null pointer dereference vulnerability has been identified in `gst_gdk_pixbuf_dec_flush` within `gstgdkpixbufdec.c`. This function invokes `memcpy`, using `out_pix` as the destination address. `out_pix` is expected to point to the frame 0 from the frame structure, which is read from the input file. However, in certain situations, it can points to a NULL frame, causing the subsequent call to `memcpy` to attempt writing to the null address (0x00), leading to a null pointer dereference. This vulnerability can result in a Denial of Service (DoS) by triggering a segmentation fault (SEGV). This vulnerability is fixed in 1.24.10.

Weakness: CWE-787 (Out-of-bounds Write), CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Gstreamer Gstreamer.

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

Upgrade to a fixed version.

## Is CVE-2024-47613 being exploited?

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

What it is: CVE-2024-47613 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47613 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-47613/ (Markdown: https://insights.sbomify.com/CVE-2024-47613/index.md)
```

## Sources

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

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