Process crash via null import pointer dereference
Published Nov 8, 2024 · Updated Nov 12, 2024
Invalid memory read in VMIR e8117 allows local users to crash the virtual machine by supplying a crafted WebAssembly file. The import_function parser follows a null pointer while processing an import declaration, causing a zero-page read and segmentation fault. Execution requires the crafted file to be opened locally; the demonstrated consequence is process termination, not code execution.
Summary
What happened
Invalid memory read in VMIR e8117 allows local users to crash the virtual machine by supplying a crafted WebAssembly file. The import_function parser follows a null pointer while processing an import declaration, causing a zero-page read and segmentation fault. Execution requires the crafted file to be opened locally; the demonstrated consequence is process termination, not code execution.
The record
- CVE
- CVE-2024-35424
- Published
- Nov 8, 2024
- Updated
- Nov 12, 2024
- Vendor
- Andreas Smas
- Product
- VMIR
- Classifications
- CWE-754, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 8, 2024CVE publishedPublication date reported by the CVE source.
- Nov 12, 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=e8117
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- VMIR import_function 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