Wasmtime can panic when adding excessive fields to a `wasi:http/types.fields` instance
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 the `wasi:http/types.fields` resource is susceptible to panics when too many fields are added to the set of headers. Wasmtime's implementation in the `wasmtime-wasi-http` crate is backed by a data structure which panics when it reaches excessive capacity and this condition was not handled gracefully in Wasmtime. Panicking in a WASI implementation is a Denial of Service vector for embedders and is treated as a security vulnerability in Wasmtime. Wasmtime 24.0.6, 36.0.6, 40.0.4, 41.0.4, and 42.0.0 patch this vulnerability and return a trap to the guest instead of panicking. There are no known workarounds at this time. Embedders are encouraged to update to a patched version of Wasmtime.
From the CVE record · GitHub_M
Wasmtime’s `wasmtime-wasi-http` implementation can panic when a guest adds too many fields to a set of HTTP headers. The panic can cause a denial of service for applications embedding Wasmtime.
Engineers embedding Wasmtime should check affected `wasmtime` crate versions: below 24.0.6, 25.0.0 through 36.0.5, 37.0.0 through 40.0.3, and 41.0.0 through 41.0.3.