Process crash via unbounded MP4 script-type read
Published Apr 25, 2022 · Updated Aug 3, 2024
Stack buffer overflow in GPAC MP4Box 2.0.0 allows local users to terminate the process by parsing a crafted MP4 file. diST_box_read reads bytes from the file into a fixed 1,024-byte stack array until a null byte appears, without enforcing the array boundary. MP4Box must parse the crafted file, and the demonstrated consequence is termination after stack-canary corruption.
Summary
What happened
Stack buffer overflow in GPAC MP4Box 2.0.0 allows local users to terminate the process by parsing a crafted MP4 file. diST_box_read reads bytes from the file into a fixed 1,024-byte stack array until a null byte appears, without enforcing the array boundary. MP4Box must parse the crafted file, and the demonstrated consequence is termination after stack-canary corruption.
The record
- CVE
- CVE-2022-1441
- Published
- Apr 25, 2022
- Updated
- Aug 3, 2024
- Vendor
- GPAC Project
- Product
- GPAC
- Classifications
- CWE-119, CWE-125, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 25, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=gpac 2.0.0
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
Public exploit references
- POC.mp4 reproduction archiveproof 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