Process crash via missing function-context validation
Published Dec 21, 2021 · Updated Aug 4, 2024
Invalid memory dereference in Binaryen 103 allows local users to crash wasm-dis by opening a crafted WebAssembly binary. WasmBinaryBuilder::visitLet reads currFunction->vars without first requiring a function context, so a let expression parsed outside that context dereferences an invalid pointer. Exploitation requires a user or integrating process to parse the crafted file, and the demonstrated consequence is a segmentation-fault process crash.
Summary
What happened
Invalid memory dereference in Binaryen 103 allows local users to crash wasm-dis by opening a crafted WebAssembly binary. WasmBinaryBuilder::visitLet reads currFunction->vars without first requiring a function context, so a let expression parsed outside that context dereferences an invalid pointer. Exploitation requires a user or integrating process to parse the crafted file, and the demonstrated consequence is a segmentation-fault process crash.
The record
- CVE
- CVE-2021-45293
- Published
- Dec 21, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119, T1204.002, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 21, 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.
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
- POC2.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