Tool crashes via missing WebAssembly end marker
Published May 23, 2023 · Updated Jan 31, 2025
Denial of service in WABT 1.0.32 allows attackers to crash wasm2c, wasm2wat, wasm-decompile, and wasm-validate with a crafted binary. The BinaryReader accepts an initializer expression without its required end opcode, leaving BinaryReaderIR with a nonempty label stack and causing an empty intrusive-list back() assertion. Exploitation requires a tool to process the malformed WebAssembly file and interrupts only that tool's process.
Summary
What happened
Denial of service in WABT 1.0.32 allows attackers to crash wasm2c, wasm2wat, wasm-decompile, and wasm-validate with a crafted binary. The BinaryReader accepts an initializer expression without its required end opcode, leaving BinaryReaderIR with a nonempty label stack and causing an empty intrusive-list back() assertion. Exploitation requires a tool to process the malformed WebAssembly file and interrupts only that tool's process.
The record
- CVE
- CVE-2023-31670
- Published
- May 23, 2023
- Updated
- Jan 31, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 23, 2023CVE publishedPublication date reported by the CVE source.
- Jan 31, 2025Record 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
- crash.wasm 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