Application crash via out-of-bounds NAL byte write
Published Jan 5, 2023 · Updated Apr 10, 2025
Heap buffer overflow in GPAC MP4Box 2.1-DEV-rev649-ga8f438d20 allows local users to crash the application via a crafted MP4 file. The gf_media_nalu_add_emulation_bytes function writes an emulation-prevention byte past its heap allocation while reformatting malformed H.264 SEI data. Processing the file through the MP4Box import path is required; public evidence demonstrates heap corruption and a crash, not code execution.
Summary
What happened
Heap buffer overflow in GPAC MP4Box 2.1-DEV-rev649-ga8f438d20 allows local users to crash the application via a crafted MP4 file. The gf_media_nalu_add_emulation_bytes function writes an emulation-prevention byte past its heap allocation while reformatting malformed H.264 SEI data. Processing the file through the MP4Box import path is required; public evidence demonstrates heap corruption and a crash, not code execution.
The record
- CVE
- CVE-2022-47661
- Published
- Jan 5, 2023
- Updated
- Apr 10, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 5, 2023CVE publishedPublication date reported by the CVE source.
- Apr 10, 2025Record 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_bof14 MP4Box crash 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