Wasmtime leaks host data with 64-bit tables and Winch
bytecodealliance wasmtime
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| wasmtime crates.io |
|
|
bytecodealliance wasmtime
| Product | Affected | Fixed in |
|---|---|---|
| wasmtime crates.io |
|
|
Wasmtime is a runtime for WebAssembly. From 25.0.0 to before 36.0.7, 42.0.2, and 43.0.1, Wasmtime's Winch compiler contains a bug where a 64-bit table, part of the memory64 proposal of WebAssembly, incorrectly translated the table.size instruction. This bug could lead to disclosing data on the host's stack to WebAssembly guests. The host's stack can possibly contain sensitive data related to other host-originating operations which is not intended to be disclosed to guests. This bug specifically arose from a mistake where the return value of table.size was statically typed as a 32-bit integer, as opposed to consulting the table's index type to see how large the returned register could be. When combined with details about Wnich's ABI, such as multi-value returns, this can be combined to read stack data from the host, within a guest. This vulnerability is fixed in 36.0.7, 42.0.2, and 43.0.1.
From the CVE record · GitHub_M
Wasmtime's Winch compiler incorrectly translates table.size for 64-bit WebAssembly tables. A WebAssembly guest using this instruction could read data from the host's stack, potentially including sensitive data from other host operations. The input does not specify network access, authentication requirements, or user interaction.
Teams running the crates.io wasmtime package should check versions >=0.0.0-0 <36.0.7, >=37.0.0 <42.0.2, and >=43.0.0 <43.0.1.