Media-processing hang via AVI length integer wrap
Published Apr 4, 2022 · Updated Aug 2, 2024
Infinite-loop handling in GPAC before 2.1.0-DEV allows local users to hang media processing with a crafted AVI file. The avidmx path passes a crafted 0xfffffff8 header size to avi_parse_input_file, whose 32-bit loop index wraps while compared with a 64-bit length. Triggering requires processing the malicious AVI through the avidmx filter; the loop consumes processing capacity without exposing or modifying data.
Summary
What happened
Infinite-loop handling in GPAC before 2.1.0-DEV allows local users to hang media processing with a crafted AVI file. The avidmx path passes a crafted 0xfffffff8 header size to avi_parse_input_file, whose 32-bit loop index wraps while compared with a 64-bit length. Triggering requires processing the malicious AVI through the avidmx filter; the loop consumes processing capacity without exposing or modifying data.
The record
- CVE
- CVE-2022-1222
- Published
- Apr 4, 2022
- Updated
- Aug 2, 2024
- Vendor
- GPAC Project
- Product
- GPAC
- Classifications
- CWE-835, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 4, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=unspecified <2.1.0-DEV
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
- Crafted AVI header proof of conceptproof of concept · demonstrated
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