Application crash via overlong NHML path
Published Jun 27, 2022 · Updated Aug 4, 2024
Heap-buffer overflow in GPAC MP4Box 1.1.0 allows local users to crash the application by importing an NHML file from a long path. In filter_parse_dyn_args, the code reallocates a path-derived heap buffer and then writes one byte immediately past its end when the absolute input path exceeds 1,024 characters. Exploitation requires the target user to invoke MP4Box on the file, and the demonstrated consequence is interruption of that MP4Box process.
Summary
What happened
Heap-buffer overflow in GPAC MP4Box 1.1.0 allows local users to crash the application by importing an NHML file from a long path. In filter_parse_dyn_args, the code reallocates a path-derived heap buffer and then writes one byte immediately past its end when the absolute input path exceeds 1,024 characters. Exploitation requires the target user to invoke MP4Box on the file, and the demonstrated consequence is interruption of that MP4Box process.
The record
- CVE
- CVE-2021-40942
- Published
- Jun 27, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 27, 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 1908 reproduction recipeproof 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