Wasmtime: WASI path_open(TRUNCATE) bypasses `FilePerms::WRITE` host restriction
bytecodealliance wasmtime
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| wasmtime-wasi crates.io |
|
|
bytecodealliance wasmtime
| Product | Affected | Fixed in |
|---|---|---|
| wasmtime-wasi crates.io |
|
|
45.0.0Wasmtime is a runtime for WebAssembly. In versions prior to 24.0.9, 36.0.10, and 44.0.2, when a filesystem preopen is given DirPerms::all() and FilePerms::READ without FilePerms::WRITE, this access control mechanism can be bypassed via the wasip2 descriptor.open-at or wasip1 path_open interfaces by opening a file with only the OpenFlags::TRUNCATE oflag. The root cause is that the clause handling OpenFlags::TRUNCATE in crates/wasi/src/filesystem.rs (Dir::open_at, lines 967–969) did not set open_mode |= OpenMode::WRITE;, which is later used for the access control check against FilePerms to determine whether opening the file is permitted; the single-line fix adds that missing assignment, after which the affected calls correctly fail with error-code.not-permitted and ERRNO_PERM respectively. Only wasmtime-wasi embeddings that combine DirPerms::MUTATE with FilePerms::READ are affected by this bug. In particular, the Wasmtime project's wasmtime-cli's use of wasmtime-wasi is not affected, because it always sets FilePerms::all() for all preopens. This issue has been fixed in versions 24.0.9, 36.0.10 and44.0.2.
From the CVE record · GitHub_M
In affected wasmtime-wasi versions, a WebAssembly guest can bypass file permissions and truncate a file by opening it with only the TRUNCATE flag through the wasip1 or wasip2 filesystem interface. This requires an embedding that combines directory mutation permission with file read permission but not file write permission. Wasmtime CLI is not affected.
Engineers using the crates.io wasmtime-wasi package should check embeddings on versions before 24.0.9, from 25.0.0 to before 36.0.10, or from 37.0.0 to before 44.0.2.