wasmtime-wasi is vulnerable to Uncontrolled Resource Consumption
59
CVE Score
Medium
Uncontrolled Resource Consumption
With stdout/stderr left unconfigured, a WASI P2 guest can call write-zeroes with a large length; the default SinkOutputStream advertises usize::MAX through check_write, so the host allocates an unbounded zero-filled buffer. Repeated calls can exhaust memory in the embedding host. The fix caps the stream's check_write permit at 64 KiB.
Upgrade the wasmtime-wasi library to the patch version.
You are affected if you are using a version that falls within the vulnerable range and run WASI guests without stdio.
0.0.1 - 36.0.16
Fixed in 36.0.1737.0.0 - 48.0.3
Fixed in 48.0.449.0.0 - 49.0.1
Fixed in 49.0.2wasmtime-wasi is vulnerable to Uncontrolled Resource Consumption in versions 0.0.1 - 36.0.16, 37.0.0 - 48.0.3 and 49.0.0 - 49.0.1.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
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.