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…
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.
Read at NIST National Vulnerability Database (CVE API 2.0)
- Vendor
- Bytecodealliance
- Product
- wasmtime
- CVSS v3.1
- 2.6 AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N
- Weakness
- CWE-20
- NVD status
- Deferred
Why it ranks 0 (Routine)
- No intrinsic risk signals yet; rank reflects source class and recency only.
- Recency: items published within 24 hours gain 15, within 72 hours 6, within 7 days 2.