Application crash via unchecked Opus channel count
Published Dec 11, 2024 · Updated Nov 3, 2025
Stack-based buffer overflow in GStreamer gst-plugins-base before 1.24.10 allows attackers to crash applications via crafted Opus audio. In gst_opus_dec_parse_header in gstopusdec.c, an unbounded loop uses an attacker-controlled channel count to write beyond the 64-entry pos stack array. The application must decode a crafted Opus header; the documented consequence is stack-control-data corruption and an application crash.
Summary
What happened
Stack-based buffer overflow in GStreamer gst-plugins-base before 1.24.10 allows attackers to crash applications via crafted Opus audio. In gst_opus_dec_parse_header in gstopusdec.c, an unbounded loop uses an attacker-controlled channel count to write beyond the 64-entry pos stack array. The application must decode a crafted Opus header; the documented consequence is stack-control-data corruption and an application crash.
The record
- CVE
- CVE-2024-47607
- Published
- Dec 11, 2024
- Updated
- Nov 3, 2025
- Vendor
- GStreamer Project
- Product
- GStreamer
- Classifications
- CWE-787, CWE-121
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 11, 2024CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.24.10
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo