Application crash via freed quantization parameter
Published Jul 19, 2022 · Updated Aug 3, 2024
Use-after-free in GPAC before 2.1-DEV allows local users to crash MP4Box by processing a crafted BIFS scene file. During BIFS multi-field decoding, BD_DecMFFieldVec removes a quantization-parameter node on one path, while Q_IsTypeOn later reads the freed node. Triggering the flaw requires a user to process the supplied file with MP4Box; the demonstrated consequence is an invalid heap read and process termination.
Summary
What happened
Use-after-free in GPAC before 2.1-DEV allows local users to crash MP4Box by processing a crafted BIFS scene file. During BIFS multi-field decoding, BD_DecMFFieldVec removes a quantization-parameter node on one path, while Q_IsTypeOn later reads the freed node. Triggering the flaw requires a user to process the supplied file with MP4Box; the demonstrated consequence is an invalid heap read and process termination.
The record
- CVE
- CVE-2022-2453
- Published
- Jul 19, 2022
- Updated
- Aug 3, 2024
- Vendor
- GPAC Project
- Product
- GPAC
- Classifications
- CWE-416, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 19, 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=unspecified <2.1-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.
Public exploit references
- poc_huaf1_s.dat MP4Box 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