Wasmtime panics when lifting `flags` component value
bytecodealliance wasmtime
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| wasmtime crates.io |
|
|
bytecodealliance wasmtime
| Product | Affected | Fixed in |
|---|---|---|
| wasmtime crates.io |
|
|
43.0.1Wasmtime 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.
From the CVE record · GitHub_M
Wasmtime can panic when lifting a flags-typed WIT interface value into Val if bits outside the defined flags are set. A guest can potentially trigger this host panic, causing a denial of service. The input does not specify network access, authentication requirements, or user interaction.
Engineers using the crates.io wasmtime package should check versions before 24.0.7, 25.0.0 through 36.0.6, 37.0.0 through 42.0.1, and 43.0.0.