Wasmtime segfault or unused out-of-sandbox load with `f64x2.splat` operator on x86-64
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, On x86-64 platforms with SSE3 disabled Wasmtime's compilation of the f64x2.splat WebAssembly instruction with Cranelift may load 8 more bytes than is necessary. When signals-based-traps are disabled this can result in a uncaught segfault due to loading from unmapped guard pages. With guard pages disabled it's possible for out-of-sandbox data to be loaded, but this data is not visible to WebAssembly guests. This vulnerability is fixed in 24.0.7, 36.0.7, 42.0.2, and 43.0.1.
From the CVE record · GitHub_M
On x86-64 with SSE3 disabled, Wasmtime’s Cranelift compilation of f64x2.splat may load eight extra bytes. If signal-based traps are disabled, this can cause an uncaught segfault; if guard pages are disabled, it can load out-of-sandbox data, though WebAssembly guests cannot see that data. The input does not specify an authentication, network, or user-interaction requirement.
Engineers using the crates.io wasmtime package should check installations older than 24.0.7, versions 25.0.0 through 36.0.6, 37.0.0 through 42.0.1, or 43.0.0.