CVE-2023-51661 – wasmer-cli

Package

Manager: cargo
Name: wasmer-cli
Vulnerable Version: >=3.0.0 <4.2.4

Severity

Level: High

CVSS v3.1: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS v4.0: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

EPSS: 0.00271 pctl0.50252

Details

Wasmer filesystem sandbox not enforced ### Summary As of Wasmer version v4.2.3, Wasm programs can access the filesystem outside of the sandbox. ### Details https://github.com/wasmerio/wasmer/issues/4267 ### PoC A minimal Rust program: ``` fn main() { let f = std::fs::OpenOptions::new() .write(true) .create_new(true) .open("abc") .unwrap(); } ``` This should be compiled with `cargo build --target wasm32-wasi`. The compiled program, when run with wasmer WITHOUT `--dir`, can still create a file in the working directory. ### Impact Service providers running untrusted Wasm code on Wasmer can unexpectedly expose the host filesystem.

Metadata

Created: 2023-12-13T13:32:38Z
Modified: 2024-01-03T16:44:36Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2023/12/GHSA-4mq4-7rw3-vm5j/GHSA-4mq4-7rw3-vm5j.json
CWE IDs: ["CWE-284"]
Alternative ID: GHSA-4mq4-7rw3-vm5j
Finding: F039
Auto approve: 1