MP4Box crash via invalid file-I/O pointer
Published Jan 7, 2022 · Updated Aug 4, 2024
Null pointer dereference in GPAC 1.0.1 allows context-dependent attackers to crash the MP4Box process via a crafted file. The gf_fileio_check function dereferences an invalid file-I/O pointer reached while MP4Box rewrites media output, raising SIGSEGV. Exploitation requires a user to process the crafted file with the MP4Box -par operation and interrupts only that process.
Summary
What happened
Null pointer dereference in GPAC 1.0.1 allows context-dependent attackers to crash the MP4Box process via a crafted file. The gf_fileio_check function dereferences an invalid file-I/O pointer reached while MP4Box rewrites media output, raising SIGSEGV. Exploitation requires a user to process the crafted file with the MP4Box -par operation and interrupts only that process.
The record
- CVE
- CVE-2021-46049
- Published
- Jan 7, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1204.002, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 7, 2022CVE 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.
Weakness, pattern, technique
Public exploit references
- POC13.zip crafted-file 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