GStreamer ASF Demuxer Heap-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GStreamer. Interaction with this library is required to exploit this vulnerability but attack vectors may vary depending on the implementation.
The specific flaw exists within the processing of stream headers within ASF files. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-28843.
A malicious ASF media file could trigger memory corruption in GStreamer and potentially run code inside the application that opens or processes it. The business risk is highest where desktops, media services, or automated ingestion pipelines handle untrusted media.
Executive priority
Prioritize patching on endpoints, servers, or services that open or process untrusted media. Treat this as high urgency for media-heavy workflows, but current sources do not support claiming active exploitation.
Technical view
The flaw is in GStreamer's ASF demuxer stream-header handling. Sources describe missing validation of user-supplied length before copying data into a fixed-length heap buffer, mapped to CWE-120 and CWE-122. CVSS is 7.8 with user interaction required.
Likely exposure
Exposure is likely where GStreamer is installed and applications process ASF files from users, email, web downloads, uploads, or media feeds. The bundle identifies GStreamer but provides limited exact affected version detail beyond a referenced commit.
Exploitation context
ZDI states attackers can execute code in the current process context, but exploitation requires interaction with the library and vectors vary by implementation. KEV is false, and the supplied sources do not state active exploitation.
Researcher notes
The strongest evidence is ZDI's description and the GStreamer commit reference. Affected-version data is incomplete in the bundle, so validation should rely on vendor package advisories and distribution status rather than inferred version ranges.
Mitigation direction
Apply GStreamer vendor fixes or distribution updates when available.
For Red Hat systems, review the listed RHSA advisories and update affected packages.
Restrict or sandbox processing of untrusted ASF files until patched.
Limit automated media ingestion from untrusted sources where GStreamer handles parsing.
Validation and detection
Inventory systems and applications using GStreamer ASF demuxing.
Check installed packages against vendor CVE and RHSA guidance.
Confirm the vendor fix commit or fixed package advisory is present.
Review media upload and ingestion paths for untrusted ASF handling.
Based on public source material and reviewed before publication.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-120: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
13Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-120 · source CWE mapping
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.