Runtime crash via out-of-bounds block-type read
Published May 6, 2024 · Updated Aug 2, 2024
Out-of-bounds read in WAMR 2.0.0 allows remote attackers to crash the runtime by supplying crafted WebAssembly bytecode. The loader's wasm_loader_prepare_bytecode path passes crafted block-type data to block_type_get_arity, which reads outside valid memory. Exploitation requires an application to load attacker-controlled bytecode through the interpreter, and the demonstrated consequence is a segmentation fault rather than data access or code execution.
Summary
What happened
Out-of-bounds read in WAMR 2.0.0 allows remote attackers to crash the runtime by supplying crafted WebAssembly bytecode. The loader's wasm_loader_prepare_bytecode path passes crafted block-type data to block_type_get_arity, which reads outside valid memory. Exploitation requires an application to load attacker-controlled bytecode through the interpreter, and the demonstrated consequence is a segmentation fault rather than data access or code execution.
The record
- CVE
- CVE-2024-34251
- Published
- May 6, 2024
- Updated
- Aug 2, 2024
- Vendor
- Bytecode Alliance
- Product
- WebAssembly Micro Runtime (WAMR)
- Classifications
- CWE-125, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 6, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=2.0.0
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.
Public exploit references
- iwasm-poc-02 testcaseproof 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