GHSA-3p27-qvp9-27qf: Medium severity rust/wasmtime-wasi vulnerability
Impact
Wasmtime's native implementation of WASIp1 suffers from a leak in the fdrenumber function where the file descriptor being renumbered to is not properly closed. Wasmtime's implementation erroneously only updated the table of descriptors for WASIp1 and didn't update the underlying table of descriptors used by the host. This behavior means that while fdrenumber works correctly from a guest's perspective it ends up leaking resources in the host that aren't cleaned up until the corresponding Store is destroyed. This means that guests can, in a loop, use fdrenumber to cause hosts to exhaust resources or exhaust file descriptors.
This bug only affects the native implementation of WASIp1. This means that only runtimes which load core wasm modules and expose fdrenumber are affected. Runtimes are additionally only affected if they expose the ability to acquire a file descriptor, such as opening a file. For runtimes that deny access to files they are unaffected.
Patches
Wasmtime 24.0.10, 36.0.11, 44.0.3, and 45.0.2 have been released which fix this issue.
Workarounds
There are no workarounds for this issue and hosts are recommended to update.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
rust/wasmtime-wasito a version that resolves this vulnerability.Fixed in 44.0.3 - Upgrade
Upgrade
rust/wasmtime-wasito a version that resolves this vulnerability.Fixed in 36.0.11 - Upgrade
Upgrade
rust/wasmtime-wasito a version that resolves this vulnerability.Fixed in 45.0.2 - Upgrade
Upgrade
rust/wasmtime-wasito a version that resolves this vulnerability.Fixed in 24.0.10 - Upgrade
Upgrade
wasmtimeto a version that resolves this vulnerability.Fixed in 24.0.10 - Upgrade
Upgrade
wasmtimeto a version that resolves this vulnerability.Fixed in 36.0.11 - Upgrade
Upgrade
wasmtimeto a version that resolves this vulnerability.Fixed in 44.0.3 - Upgrade
Upgrade
wasmtimeto a version that resolves this vulnerability.Fixed in 45.0.2
Event History
Frequently Asked Questions
Which deployments are affected?
Only Wasmtime runtimes using the native WASIp1 implementation, loading core WebAssembly modules, and exposing both fd_renumber and a way for guests to acquire file descriptors, such as opening files, are affected. Runtimes that deny file access are unaffected.
What does an attacker need to do to trigger the issue?
A guest needs the ability to acquire file descriptors and invoke fd_renumber repeatedly. This can leak host-side resources or file descriptors until the relevant Store is destroyed, potentially exhausting host resources.
Are there mitigations if an update cannot be applied immediately?
No workaround is available. Hosts are recommended to update to a fixed release.
Which releases contain the fix?
Fixed releases are Wasmtime 24.0.10, 36.0.11, 44.0.3, and 45.0.2.