Process crash via stale descriptor double free
Published Dec 21, 2021 · Updated Aug 4, 2024
Double free in MP4Box in GPAC 1.0.1 allows local users to crash the process by processing a crafted multimedia file. In gf_sm_load_run_isom, error branches delete an ESD descriptor without clearing the pointer, so later cleanup frees the same allocation again. The user must cause MP4Box to process the file with scene-dump handling; the demonstrated consequence is a SIGABRT process crash.
Summary
What happened
Double free in MP4Box in GPAC 1.0.1 allows local users to crash the process by processing a crafted multimedia file. In gf_sm_load_run_isom, error branches delete an ESD descriptor without clearing the pointer, so later cleanup frees the same allocation again. The user must cause MP4Box to process the file with scene-dump handling; the demonstrated consequence is a SIGABRT process crash.
The record
- CVE
- CVE-2021-45288
- Published
- Dec 21, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 21, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.zip MP4Box crash reproducerproof 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