VYPR
Unrated severityNVD Advisory· Published Apr 19, 2021· Updated Aug 3, 2024

CVE-2021-3498

CVE-2021-3498

Description

Heap corruption in GStreamer's Matroska demuxer (gst-plugins-good before 1.18.4) allows arbitrary code execution via a crafted file.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Heap corruption in GStreamer's Matroska demuxer (gst-plugins-good before 1.18.4) allows arbitrary code execution via a crafted file.

Vulnerability

A heap corruption vulnerability exists in the Matroska demuxer of GStreamer's gst-plugins-good library, affecting versions 1.x up to and including 1.18.3 [2][4]. The bug is triggered when parsing specially crafted malformed Matroska media files, leading to memory corruption.

Exploitation

An attacker can exploit this vulnerability by crafting a malicious Matroska file and delivering it to a target user. No authentication is required; the user must open the file with an application that uses GStreamer (e.g., a media player). The parsing of the malformed data causes heap corruption, which may be leveraged for code execution.

Impact

Successful exploitation could result in a denial of service (application crash) or, potentially, arbitrary code execution with the privileges of the user running the vulnerable application [4]. The impact is limited to the user's context.

Mitigation

The issue is fixed in GStreamer gst-plugins-good version 1.18.4 [4]. Users should upgrade to this version or later. Gentoo users can update to >=media-libs/gst-plugins-good-1.20.2 [3]. A patch is available from the GStreamer project [4]. No workaround is known.

AI Insight generated on May 27, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

6

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

5

News mentions

0

No linked articles in our index yet.