Interpreter crash via invalid return-call type read
Published Oct 28, 2022 · Updated May 8, 2025
Out-of-bounds read in WebAssembly WABT wasm-interp 1.0.29 allows local users to crash it with a crafted WebAssembly module. While parsing a return_call_indirect expression, OnReturnCallIndirectExpr calls GetReturnCallDropKeepCount, which reads an invalid FuncType vector while computing stack drop and keep counts. A local user must supply the module and enable all WebAssembly features; the demonstrated consequence is an interpreter crash.
Summary
What happened
Out-of-bounds read in WebAssembly WABT wasm-interp 1.0.29 allows local users to crash it with a crafted WebAssembly module. While parsing a return_call_indirect expression, OnReturnCallIndirectExpr calls GetReturnCallDropKeepCount, which reads an invalid FuncType vector while computing stack drop and keep counts. A local user must supply the module and enable all WebAssembly features; the demonstrated consequence is an interpreter crash.
The record
- CVE
- CVE-2022-43282
- Published
- Oct 28, 2022
- Updated
- May 8, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 28, 2022CVE publishedPublication date reported by the CVE source.
- May 8, 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?
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.
Public exploit references
- poc-interp-3.wasm proof of conceptproof 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