Wasmtime before 36.0.18, 37.0.0 before 48.0.6, and 49.0.0 before 49.0.3 HTTP Request Target Smuggling
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 36.0.18, 48.0.6, 49.0.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Wasmtime, the WebAssembly runtime, and its wasmtime-wasi-http component are affected. A malicious guest module can send HTTP requests that bypass the embedder's host filtering policies and reach destinations the policy was meant to block, by way of a forward proxy or gateway at the permitted address.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Wasmtime before 36.0.18, 37.0.0 before 48.0.6, and 49.0.0 before 49.0.3 does not verify that set-path-with-query values in wasmtime-wasi-http are paths, so absolute-form URLs are written verbatim as the HTTP/1.1 request target while the connection uses the allowed authority. A malicious guest can supply an absolute URL that a forward proxy or gateway at that authority honors, reaching hosts disallowed by embedder filtering policies.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- bytecodealliance wasmtime
fixed in 36.0.18; From 37.0.0 · fixed in 48.0.6; From 49.0.0 · fixed in 49.0.3
- wasmtime-wasi-httpcrates.io
From 0.0.0-0 · fixed in 36.0.18; From 37.0.0 · fixed in 48.0.6; From 49.0.0 · fixed in 49.0.3