Application crash via unchecked LASeR stream pointer
Published Dec 22, 2021 · Updated Aug 4, 2024
Invalid memory dereference in GPAC 1.1.0 allows local users to crash MP4Box by processing a crafted LASeR scene file. While parsing the crafted XSR input, svg_node_start uses parser->laser_es without checking whether it is null, then reads its AUs member. The user must cause MP4Box to open the file; the demonstrated consequence is a segmentation fault and process crash, with no reported data exposure or code execution.
Summary
What happened
Invalid memory dereference in GPAC 1.1.0 allows local users to crash MP4Box by processing a crafted LASeR scene file. While parsing the crafted XSR input, svg_node_start uses parser->laser_es without checking whether it is null, then reads its AUs member. The user must cause MP4Box to open the file; the demonstrated consequence is a segmentation fault and process crash, with no reported data exposure or code execution.
The record
- CVE
- CVE-2021-45267
- Published
- Dec 22, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 22, 2021CVE 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
- poc_2.xsr crash 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