Process crash via post-read scene-parser bounds check
Published Sep 5, 2023 · Updated Sep 27, 2024
Out-of-bounds read in GPAC before 2.3-DEV allows local users to crash MP4Box by processing a crafted scene-description file. The gf_bt_get_next function reads line_buffer before checking whether line_pos plus its index has reached line_size. The file must enter MP4Box's DASH workflow and be parsed; the demonstrated consequence is a process crash.
Summary
What happened
Out-of-bounds read in GPAC before 2.3-DEV allows local users to crash MP4Box by processing a crafted scene-description file. The gf_bt_get_next function reads line_buffer before checking whether line_pos plus its index has reached line_size. The file must enter MP4Box's DASH workflow and be parsed; the demonstrated consequence is a process crash.
The record
- CVE
- CVE-2023-4778
- Published
- Sep 5, 2023
- Updated
- Sep 27, 2024
- Vendor
- GPAC Project
- Product
- GPAC
- Classifications
- CWE-125, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 5, 2023CVE publishedPublication date reported by the CVE source.
- Sep 27, 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.
Public exploit references
- POC_crash000362 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