Code execution via unbounded parser error formatting
Published Jul 26, 2024 · Updated Feb 13, 2025
Stack buffer overflow in GStreamer Orc before 0.4.39 allows attackers to execute code by supplying a malformed Orc source file. orc_parse_add_error_valist in orcparse.c passes attacker-influenced error text to unbounded vsprintf formatting that can overrun a fixed-size stack buffer. Exploitation requires a developer or CI job to process the file with orcc; liborc users are unaffected, and code runs with the compiler process's privileges.
Summary
What happened
Stack buffer overflow in GStreamer Orc before 0.4.39 allows attackers to execute code by supplying a malformed Orc source file. orc_parse_add_error_valist in orcparse.c passes attacker-influenced error text to unbounded vsprintf formatting that can overrun a fixed-size stack buffer. Exploitation requires a developer or CI job to process the file with orcc; liborc users are unaffected, and code runs with the compiler process's privileges.
The record
- CVE
- CVE-2024-40897
- Published
- Jul 26, 2024
- Updated
- Feb 13, 2025
- Vendor
- GStreamer Project
- Product
- Orc
- Classifications
- CWE-787, CWE-121, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 26, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 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=0 <0.4.39
- Affected versionversion=prior to 0.4.39
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
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