Application crash via unchecked profile buffer read
Published Apr 14, 2023 · Updated Feb 6, 2025
Heap buffer overflow in MP4v2 before 2.1.3 allows attackers to crash applications by supplying a crafted MP4 file. MP4GetVideoProfileLevel obtains a one-byte elementary-stream configuration buffer, then reads four bytes from it without validating the returned size. Processing the attacker-controlled file is required; the published proof demonstrates an out-of-bounds read and process abort, not code execution.
Summary
What happened
Heap buffer overflow in MP4v2 before 2.1.3 allows attackers to crash applications by supplying a crafted MP4 file. MP4GetVideoProfileLevel obtains a one-byte elementary-stream configuration buffer, then reads four bytes from it without validating the returned size. Processing the attacker-controlled file is required; the published proof demonstrates an out-of-bounds read and process abort, not code execution.
The record
- CVE
- CVE-2023-29584
- Published
- Apr 14, 2023
- Updated
- Feb 6, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 14, 2023CVE publishedPublication date reported by the CVE source.
- Feb 6, 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
- MP4GetVideoProfileLevel 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