Wasmtime request smuggling in WASI HTTP outgoing requests
bytecodealliance wasmtime
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| wasmtime-wasi-http crates.io |
|
|
bytecodealliance wasmtime
| Product | Affected | Fixed in |
|---|---|---|
| wasmtime-wasi-http crates.io |
|
|
The wasmtime-wasi-http p2 implementation in Wasmtime before 36.0.20, 37.0.0 before 48.0.8, 49.0.0 before 49.0.5, and 50.0.0 before 50.0.1 can send conflicting content-length headers, or ones not matching the body, in outgoing requests. A guest that reuses a received response's headers resource to send a bodyless request can enable request smuggling against non-compliant servers, potentially bypassing embedder destination access controls.
From the CVE record · VulnCheck
The wasmtime-wasi-http p2 implementation can send outgoing requests with conflicting content-length headers or headers that do not match the body. If a guest reuses headers from a received response to send a bodyless request, request smuggling against a non-compliant server could bypass the embedder's destination access controls.
Engineers running Wasmtime with the crates.io wasmtime-wasi-http package should check versions >=0.0.0-0 <36.0.20, >=37.0.0 <48.0.8, >=49.0.0 <49.0.5, and >=50.0.0 <50.0.1.