Crash via unbounded nested expression parsing
Published Jan 7, 2022 · Updated Aug 4, 2024
Stack exhaustion in Binaryen 103 allows context-dependent attackers to crash wasm-ctor-eval with a crafted WebAssembly file. The WasmBinaryBuilder parser repeatedly descends nested try and block expressions without a depth limit until the process stack is exhausted. Reachability requires processing a crafted WebAssembly file with wasm-ctor-eval; the demonstrated consequence is a segmentation-fault crash, not data disclosure or modification.
Summary
What happened
Stack exhaustion in Binaryen 103 allows context-dependent attackers to crash wasm-ctor-eval with a crafted WebAssembly file. The WasmBinaryBuilder parser repeatedly descends nested try and block expressions without a depth limit until the process stack is exhausted. Reachability requires processing a crafted WebAssembly file with wasm-ctor-eval; the demonstrated consequence is a segmentation-fault crash, not data disclosure or modification.
The record
- CVE
- CVE-2021-46050
- Published
- Jan 7, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-770, 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.
Weakness, pattern, technique
Public exploit references
- POC4.zip 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