Application crash via null child-box dereference
Published Jul 21, 2021 · Updated Aug 4, 2024
Null pointer dereference in GPAC MP4Box 0.8.0 allows attackers to crash the application via a crafted MP4 file. In ilst_item_box_read, gf_isom_box_parse can leave the child-box pointer null without an error, but the code dereferences its size member. Exploitation requires a local MP4Box invocation against the malformed file; the observed consequence is a segmentation-fault crash.
Summary
What happened
Null pointer dereference in GPAC MP4Box 0.8.0 allows attackers to crash the application via a crafted MP4 file. In ilst_item_box_read, gf_isom_box_parse can leave the child-box pointer null without an error, but the code dereferences its size member. Exploitation requires a local MP4Box invocation against the malformed file; the observed consequence is a segmentation-fault crash.
The record
- CVE
- CVE-2020-19488
- Published
- Jul 21, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 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_npd_ilst_item_Readproof 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