Process crash via undersized ftyp atom
Published Apr 24, 2023 · Updated Feb 4, 2025
Heap buffer overflow in mp4v2 2.0.0 allows context-dependent attackers to crash a consuming process via a crafted MP4 file. An ftyp atom smaller than its header underflows the parsed size, producing an oversized brand count whose allocation wraps before the destructor iterates past the string-pointer array. Processing the file is required; the demonstrated result is an AddressSanitizer abort caused by an out-of-bounds pointer read and invalid free.
Summary
What happened
Heap buffer overflow in mp4v2 2.0.0 allows context-dependent attackers to crash a consuming process via a crafted MP4 file. An ftyp atom smaller than its header underflows the parsed size, producing an oversized brand count whose allocation wraps before the destructor iterates past the string-pointer array. Processing the file is required; the demonstrated result is an AddressSanitizer abort caused by an out-of-bounds pointer read and invalid free.
The record
- CVE
- CVE-2023-29578
- Published
- Apr 24, 2023
- Updated
- Feb 4, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 24, 2023CVE publishedPublication date reported by the CVE source.
- Feb 4, 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
- Crafted MP4 process-abort reproducerproof 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