Wasmtime WASI implementations are vulnerable to guest-controlled resource exhaustion
bytecodealliance wasmtime
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| wasmtime crates.io |
|
|
bytecodealliance wasmtime
| Product | Affected | Fixed in |
|---|---|---|
| wasmtime crates.io |
|
|
41.0.4Wasmtime is a runtime for WebAssembly. Prior to versions 24.0.6, 36.0.6, 4.0.04, 41.0.4, and 42.0.0, Wasmtime's implementation of WASI host interfaces are susceptible to guest-controlled resource exhaustion on the host. Wasmtime did not appropriately place limits on resource allocations requested by the guests. This serves as a Denial of Service vector. Wasmtime 24.0.6, 36.0.6, 40.0.4, 41.0.4, and 42.0.0 have all been released with the fix for this issue. These versions do not prevent this issue in their default configuration to avoid breaking preexisting behaviors. All versions of Wasmtime have appropriate knobs to prevent this behavior, and Wasmtime 42.0.0-and-later will have these knobs tuned by default to prevent this issue from happening. There are no known workarounds for this issue without upgrading. Embedders are recommended to upgrade and configure their embeddings as necessary to prevent possibly-malicious guests from triggering this issue.
From the CVE record · GitHub_M
Wasmtime's WASI host interfaces can allow a WebAssembly guest to request excessive host resources, causing a denial of service. An attacker must be able to run a guest in an affected Wasmtime embedding; the input does not specify network access or authentication requirements. Fixed releases before 42.0.0 still require configuration to prevent this behavior.
Engineers embedding Wasmtime should check affected crates.io wasmtime versions below 24.0.6, 25.0.0–36.0.5, 37.0.0–40.0.3, and 41.0.0–41.0.3.