Wasmtime before 36.0.20 HTTP Request Smuggling via wasi-http p2 Content-Length
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| bytecodealliance | wasmtime | unaffected |
|
|||||||||
| bytecodealliance | wasmtime | unaffected |
|
|||||||||
| bytecodealliance | wasmtime | unaffected |
|
|||||||||
| bytecodealliance | wasmtime | unaffected |
|
No data.
No data.
No data available yet.
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Wasmtime before 36.0.20 HTTP Request Smuggling via wasi-http p2 Content-Length | |
| First Time appeared |
Bytecodealliance
Bytecodealliance wasmtime |
|
| Weaknesses | CWE-444 | |
| CPEs | cpe:2.3:a:bytecodealliance:wasmtime:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Bytecodealliance
Bytecodealliance wasmtime |
|
| References |
| |
| Metrics |
cvssV3_1
|