wasm-opt crash via exception-target assertion failure
Published Jan 7, 2022 · Updated Aug 4, 2024
Reachable assertion in WebAssembly Binaryen 104 allows context-dependent attackers to crash wasm-opt via a crafted WebAssembly file. WasmBinaryBuilder::readFunctions asserts that exceptionTargetNames is empty instead of rejecting a malformed module, causing SIGABRT when the check fails. Exploitation requires user interaction with the crafted file and terminates only the current wasm-opt process.
Summary
What happened
Reachable assertion in WebAssembly Binaryen 104 allows context-dependent attackers to crash wasm-opt via a crafted WebAssembly file. WasmBinaryBuilder::readFunctions asserts that exceptionTargetNames is empty instead of rejecting a malformed module, causing SIGABRT when the check fails. Exploitation requires user interaction with the crafted file and terminates only the current wasm-opt process.
The record
- CVE
- CVE-2021-46048
- Published
- Jan 7, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-617, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 7, 2022CVE 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
- POC7.zipproof 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