Process crash via invalid scene-graph pointer
Published Jan 21, 2022 · Updated Aug 4, 2024
NULL pointer dereference in GPAC 1.1.0 allows local users to crash MP4Box by having a crafted SVG file processed. gf_node_unregister dereferences an invalid scene-graph pointer while unregistering a node derived from the crafted SVG content. A user must cause MP4Box to process the file; the demonstrated consequence is a segmentation fault and process crash.
Summary
What happened
NULL pointer dereference in GPAC 1.1.0 allows local users to crash MP4Box by having a crafted SVG file processed. gf_node_unregister dereferences an invalid scene-graph pointer while unregistering a node derived from the crafted SVG content. A user must cause MP4Box to process the file; the demonstrated consequence is a segmentation fault and process crash.
The record
- CVE
- CVE-2021-46237
- Published
- Jan 21, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1204.002, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 21, 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
- POC2.zip crafted SVG crash reproducerproof 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