Local wasm-ctor-eval termination via crafted input
Published Jan 7, 2022 · Updated Aug 4, 2024
Denial of service in WebAssembly Binaryen 103 allows local users to terminate wasm-ctor-eval with SIGKILL using a crafted input file. The upstream report identifies the affected tool and POC5 input, but it provides no stack trace or function-level explanation of the operation that triggers the kill. Reproduction requires local execution of wasm-ctor-eval against the crafted file, and the demonstrated consequence is termination of that process.
Summary
What happened
Denial of service in WebAssembly Binaryen 103 allows local users to terminate wasm-ctor-eval with SIGKILL using a crafted input file. The upstream report identifies the affected tool and POC5 input, but it provides no stack trace or function-level explanation of the operation that triggers the kill. Reproduction requires local execution of wasm-ctor-eval against the crafted file, and the demonstrated consequence is termination of that process.
The record
- CVE
- CVE-2021-46053
- Published
- Jan 7, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119, T1499
- 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- POC5 crafted-input 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