Crash via unchecked AVI bitmap header length
Published Sep 4, 2023 · Updated Sep 19, 2024
Buffer over-read in GPAC before 2.3-DEV allows local users to crash MP4Box during DASH conversion of a crafted AVI file. The avi_parse_input_file function trusts the AVI bitmap header's bi_size field and copies that many bytes from hdrl_data without checking the remaining header length. Processing the file is sufficient to trigger an out-of-bounds heap read, terminating the process without reported code execution.
Summary
What happened
Buffer over-read in GPAC before 2.3-DEV allows local users to crash MP4Box during DASH conversion of a crafted AVI file. The avi_parse_input_file function trusts the AVI bitmap header's bi_size field and copies that many bytes from hdrl_data without checking the remaining header length. Processing the file is sufficient to trigger an out-of-bounds heap read, terminating the process without reported code execution.
The record
- CVE
- CVE-2023-4758
- Published
- Sep 4, 2023
- Updated
- Sep 19, 2024
- Vendor
- GPAC Project
- Product
- GPAC
- Classifications
- CWE-125, CWE-126, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 4, 2023CVE publishedPublication date reported by the CVE source.
- Sep 19, 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=unspecified <2.3-DEV
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
- GPAC issue 2573 crash4 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