Application crash via unused compiler-slot sentinel
Published Dec 31, 2021 · Updated Aug 4, 2024
Out-of-bounds write in CompileBlock in Wasm3 0.5.0 allows local users to crash an application by loading crafted WebAssembly. When restoring block parameters to the compiler stack, CompileBlock can pass the c_slotUnused sentinel from GetSlotForStackIndex to MarkSlotsAllocatedByType, which writes outside the slot table. A user must cause an application embedding Wasm3 to compile a crafted module; the documented consequence is a process crash.
Summary
What happened
Out-of-bounds write in CompileBlock in Wasm3 0.5.0 allows local users to crash an application by loading crafted WebAssembly. When restoring block parameters to the compiler stack, CompileBlock can pass the c_slotUnused sentinel from GetSlotForStackIndex to MarkSlotsAllocatedByType, which writes outside the slot table. A user must cause an application embedding Wasm3 to compile a crafted module; the documented consequence is a process crash.
The record
- CVE
- CVE-2021-45946
- Published
- Dec 31, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 31, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
No public exploit references are available in this record.
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