Process crash via out-of-bounds read in wasm_call
Published Nov 8, 2024 · Updated Mar 14, 2025
Heap buffer overflow in the wasm_call parser in Andreas Smas VMIR e8117 allows local users to crash its process via a crafted WebAssembly file. The function performs an eight-byte read from eight bytes before an 11-byte heap allocation created for a named basic block while loading the module. Execution of attacker-supplied WebAssembly and user interaction are required; the public report demonstrates a process crash, not code execution.
Summary
What happened
Heap buffer overflow in the wasm_call parser in Andreas Smas VMIR e8117 allows local users to crash its process via a crafted WebAssembly file. The function performs an eight-byte read from eight bytes before an 11-byte heap allocation created for a named basic block while loading the module. Execution of attacker-supplied WebAssembly and user interaction are required; the public report demonstrates a process crash, not code execution.
The record
- CVE
- CVE-2024-35422
- Published
- Nov 8, 2024
- Updated
- Mar 14, 2025
- Vendor
- Andreas Smas
- Product
- VMIR
- Classifications
- CWE-120, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 8, 2024CVE publishedPublication date reported by the CVE source.
- Mar 14, 2025Record 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 wasm_call 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