Process crash via undersized MPEG header
Published Jan 13, 2022 · Updated Aug 4, 2024
Null pointer dereference in GPAC MP4Box 1.0.1 allows local users to crash the process by opening a crafted MPEG video file. In mpgviddmx_process, fewer than five remaining bytes reach header parsing, causing memcpy to receive a size of -1. Exploitation requires a user to run MP4Box against the crafted file; the demonstrated consequence is termination of that MP4Box process.
Summary
What happened
Null pointer dereference in GPAC MP4Box 1.0.1 allows local users to crash the process by opening a crafted MPEG video file. In mpgviddmx_process, fewer than five remaining bytes reach header parsing, causing memcpy to receive a size of -1. Exploitation requires a user to run MP4Box against the crafted file; the demonstrated consequence is termination of that MP4Box process.
The record
- CVE
- CVE-2021-40575
- Published
- Jan 13, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 13, 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.
Public exploit references
- GPAC issue 1905 proof-of-concept fileproof 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