wasmtime-wasi-http is vulnerable to Uncontrolled Resource Consumption
62
Medium Risk
wasmtime-wasi-http does not enforce the write allowance that wasi:io/streams.check-write returns for WASIp2 outgoing HTTP bodies. A guest can call check-write, read the configured chunk-size allowance, and then pass a larger buffer to write, which succeeds instead of trapping as the spec requires. Each outgoing-body resource the guest creates can therefore hold at least one linear-memory-sized host allocation for the life of the guest's store. The fix rejects writes that exceed the write budget returned by check-write.
You are affected if you are using a version that falls within the vulnerable range and you use wasmtime-wasi-http to serve WASIp2 outgoing HTTP requests or responses from guest code.
wasmtime-wasi-http is vulnerable to Uncontrolled Resource Consumption in versions 0.0.1 - 36.0.15, 37.0.0 - 48.0.2 and 49.0.0 - 49.0.0.
Upgrade the wasmtime-wasi-http library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.