Process crash via unchecked G.729 channel count
Published May 2, 2022 · Updated Aug 3, 2024
Integer overflow in FFmpeg 4.2 through 4.4.1 and 5.0 allows local users to crash the process via a crafted G.729 file. The g729_parse function multiplies the parser block size by an unchecked channel count, allowing signed integer overflow and an assertion failure. Triggering requires processing attacker-supplied G.729 content; the documented consequence is interruption of that FFmpeg process.
Summary
What happened
Integer overflow in FFmpeg 4.2 through 4.4.1 and 5.0 allows local users to crash the process via a crafted G.729 file. The g729_parse function multiplies the parser block size by an unchecked channel count, allowing signed integer overflow and an assertion failure. Triggering requires processing attacker-supplied G.729 content; the documented consequence is interruption of that FFmpeg process.
The record
- CVE
- CVE-2022-1475
- Published
- May 2, 2022
- Updated
- Aug 3, 2024
- Vendor
- FFmpeg
- Product
- FFmpeg
- Classifications
- CWE-190, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 2, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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=before 4.4.2
- Affected versionversion=before 5.0.1
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