Wasmtime: Leak in WASIp1 `fd_renumber` implementation
bytecodealliance wasmtime
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| wasmtime-wasi crates.io |
|
|
bytecodealliance wasmtime
| Product | Affected | Fixed in |
|---|---|---|
| wasmtime-wasi crates.io |
|
|
44.0.3Wasmtime is a runtime for WebAssembly. All versions prior to 24.0.10; versions 25.0.0 through those before 36.0.11; versions 37.0.0 through those before 44.0.3; and versions 45.0.0 and 45.0.1 contain a native implementation of WASIp1 which suffers from a leak in the fd_renumber 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 fd_renumber 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. In a loop, guests can use fd_renumber to cause hosts to exhaust both resources and file descriptors. This bug only affects the native implementation of WASIp1, meaning that only runtimes which load core wasm modules and expose fd_renumber 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. This issue has been fixed in versions 24.0.10, 36.0.11, 44.0.3, and 45.0.2.
From the CVE record · GitHub_M
Wasmtime’s native WASIp1 implementation leaks host file descriptors when a guest calls fd_renumber. A guest can repeatedly call it to exhaust host resources if the runtime loads core WebAssembly modules, exposes fd_renumber, and lets guests acquire file descriptors, such as by opening files.
Operators using wasmtime-wasi versions before 24.0.10, 25.0.0–36.0.10, 37.0.0–44.0.2, or 45.0.0–45.0.1 should check their runtime configuration.