Wasmtime panics when lifting `flags` component value
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 24.0.7, 36.0.7, 42.0.2, 44.0.1, 43.0.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
Wasmtime is a runtime for WebAssembly. Prior to 24.0.7, 36.0.7, 42.0.2, and 43.0.1, Wasmtime contains a possible panic which can happen when a flags-typed component model value is lifted with the Val type. If bits are set outside of the set of flags the component model specifies that these bits should be ignored but Wasmtime will panic when this value is lifted. This panic only affects wasmtime's implementation of lifting into Val, not when using the flags! macro. This additionally only affects flags-typed values which are part of a WIT interface. This has the risk of being a guest-controlled panic within the host which Wasmtime considers a DoS vector. This vulnerability is fixed in 24.0.7, 36.0.7, 42.0.2, and 43.0.1.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- bytecodealliance wasmtime
fixed in 24.0.7; From 25.0.0 · fixed in 36.0.7; From 37.0.0 · fixed in 42.0.2; From 43.0.0 · fixed in 44.0.1
- wasmtimecrates.io
From 0.0.0-0 · fixed in 24.0.7; From 25.0.0 · fixed in 36.0.7; From 37.0.0 · fixed in 42.0.2; From 43.0.0 · fixed in 43.0.1
- wasmtimecrates.io
fixed in 24.0.7
- wasmtimecrates.io
From 25.0.0 · fixed in 36.0.7
- wasmtimecrates.io
From 37.0.0 · fixed in 42.0.2
- wasmtimecrates.io
From 43.0.0 · fixed in 43.0.1