Application crash via invalid identifier dereference
Published Jan 14, 2022 · Updated Aug 4, 2024
Memory-safety flaw in GPAC 1.1.0 allows local users to crash MP4Box by opening a crafted MPEG-4 LASeR scene file. The lsr_read_id() parser follows an attacker-controlled identifier to an invalid address while decoding LASeR scene elements, triggering a segmentation fault. Exploitation requires a user to run MP4Box against the file, and the demonstrated consequence is termination of that process rather than code execution.
Summary
What happened
Memory-safety flaw in GPAC 1.1.0 allows local users to crash MP4Box by opening a crafted MPEG-4 LASeR scene file. The lsr_read_id() parser follows an attacker-controlled identifier to an invalid address while decoding LASeR scene elements, triggering a segmentation fault. Exploitation requires a user to run MP4Box against the file, and the demonstrated consequence is termination of that process rather than code execution.
The record
- CVE
- CVE-2021-45767
- Published
- Jan 14, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 14, 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.
Weakness, pattern, technique
Public exploit references
- lsr_read_id proof-of-concept file setproof 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