Memory corruption via unchecked MPEG payload length
Published Jan 10, 2022 · Updated Aug 4, 2024
Heap-based buffer overflow in GPAC MP4Box 1.0.1 allows context-dependent attackers to corrupt memory via a crafted MPEG video file. During RTP hinting, gp_rtp_builder_do_mpeg12_video reads payload[4] without verifying that certain MPEG picture payloads contain five bytes. Exploitation requires MP4Box to process the file with its hinting operation; the published proof of concept produces an out-of-bounds read and process abort, while broader impact is unspecified.
Summary
What happened
Heap-based buffer overflow in GPAC MP4Box 1.0.1 allows context-dependent attackers to corrupt memory via a crafted MPEG video file. During RTP hinting, gp_rtp_builder_do_mpeg12_video reads payload[4] without verifying that certain MPEG picture payloads contain five bytes. Exploitation requires MP4Box to process the file with its hinting operation; the published proof of concept produces an out-of-bounds read and process abort, while broader impact is unspecified.
The record
- CVE
- CVE-2021-36412
- Published
- Jan 10, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 10, 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 1838 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