Interpreter crash via code-page out-of-bounds write
Published Apr 16, 2022 · Updated Aug 3, 2024
Heap-based buffer overflow in Wasm3 0.5.0 allows local users to crash the interpreter by compiling a crafted WebAssembly module. During branch-table compilation, NewCodePage allocates a one-byte heap region and then performs a four-byte write 15 bytes past that region. Execution requires a user or embedding application to compile attacker-supplied WebAssembly; the demonstrated consequence is heap corruption and process termination.
Summary
What happened
Heap-based buffer overflow in Wasm3 0.5.0 allows local users to crash the interpreter by compiling a crafted WebAssembly module. During branch-table compilation, NewCodePage allocates a one-byte heap region and then performs a four-byte write 15 bytes past that region. Execution requires a user or embedding application to compile attacker-supplied WebAssembly; the demonstrated consequence is heap corruption and process termination.
The record
- CVE
- CVE-2022-28966
- Published
- Apr 16, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 16, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
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.zip WebAssembly 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