Process crash via out-of-bounds function-type lookup
Published Oct 28, 2022 · Updated May 7, 2025
An out-of-bounds read in WABT wasm-interp 1.0.29 allows context-dependent attackers to crash it with a crafted WebAssembly module. While reading the module, GetReturnCallDropKeepCount obtains func_type.params.size() from an invalid FuncType reference and reads beyond the vector allocation. Exploitation requires a user or consuming application to process the malicious module; the demonstrated consequence is a segmentation fault and process abort.
Summary
What happened
An out-of-bounds read in WABT wasm-interp 1.0.29 allows context-dependent attackers to crash it with a crafted WebAssembly module. While reading the module, GetReturnCallDropKeepCount obtains func_type.params.size() from an invalid FuncType reference and reads beyond the vector allocation. Exploitation requires a user or consuming application to process the malicious module; the demonstrated consequence is a segmentation fault and process abort.
The record
- CVE
- CVE-2022-43280
- Published
- Oct 28, 2022
- Updated
- May 7, 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 7, 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-2.wasmproof 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