Conversion hang via post-validation name generation
Published May 3, 2023 · Updated Jan 30, 2025
Infinite-loop handling in WABT wasm2c 1.0.32 allows local users to hang conversion by supplying a malformed WebAssembly binary. The wasm2c workhorse continued into GenerateNames after module validation failed instead of returning the validation error, so malformed type data drove invalid processing. Exploitation requires a user or automated workflow to run wasm2c on the crafted file, interrupting that conversion process.
Summary
What happened
Infinite-loop handling in WABT wasm2c 1.0.32 allows local users to hang conversion by supplying a malformed WebAssembly binary. The wasm2c workhorse continued into GenerateNames after module validation failed instead of returning the validation error, so malformed type data drove invalid processing. Exploitation requires a user or automated workflow to run wasm2c on the crafted file, interrupting that conversion process.
The record
- CVE
- CVE-2023-30300
- Published
- May 3, 2023
- Updated
- Jan 30, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-835, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 3, 2023CVE publishedPublication date reported by the CVE source.
- Jan 30, 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
- hang.wasm proof of conceptproof 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