Filesystem sandbox not enforced in wasmer-cli
cve-program · CVE-2023-51661
PublishedWasmer is a WebAssembly runtime that enables containers to run anywhere: from Desktop to the Cloud, Edge and even the browser. Wasm programs can access the filesystem outside of the sandbox. Service providers running untrusted Wasm code on Wasmer can unexpectedly expose the host filesystem. This vulnerability has been patched in version 4.2.4.
Read the publisher's advisoryeuvd · EUVD-2023-3103
PublishedWasmer is a WebAssembly runtime that enables containers to run anywhere: from Desktop to the Cloud, Edge and even the browser. Wasm programs can access the filesystem outside of the sandbox. Service providers running untrusted Wasm code on Wasmer can unexpectedly expose the host filesystem. This vulnerability has been patched in version 4.2.4.
Read the publisher's advisorynvd · CVE-2023-51661
PublishedWasmer is a WebAssembly runtime that enables containers to run anywhere: from Desktop to the Cloud, Edge and even the browser. Wasm programs can access the filesystem outside of the sandbox. Service providers running untrusted Wasm code on Wasmer can unexpectedly expose the host filesystem. This vulnerability has been patched in version 4.2.4.
Read the publisher's advisoryosv · GHSA-4mq4-7rw3-vm5j
Published### 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.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2023-51661 · CVE overview and exploitation status
cve-program · CVE-2023-51661
- https://github.com/wasmerio/wasmer/security/advisories/GHSA-4mq4-7rw3-vm5j
- https://github.com/wasmerio/wasmer/issues/4267
- https://github.com/wasmerio/wasmer/commit/4d63febf9d8b257b0531963b85df48d45d0dbf3c
euvd · EUVD-2023-3103
- https://github.com/wasmerio/wasmer/security/advisories/GHSA-4mq4-7rw3-vm5j
- https://github.com/wasmerio/wasmer/issues/4267
- https://github.com/wasmerio/wasmer/commit/4d63febf9d8b257b0531963b85df48d45d0dbf3c
nvd · CVE-2023-51661
- https://github.com/wasmerio/wasmer/commit/4d63febf9d8b257b0531963b85df48d45d0dbf3c
- https://github.com/wasmerio/wasmer/issues/4267
- https://github.com/wasmerio/wasmer/security/advisories/GHSA-4mq4-7rw3-vm5j
osv · GHSA-4mq4-7rw3-vm5j
- https://github.com/wasmerio/wasmer/security/advisories/GHSA-4mq4-7rw3-vm5j
- https://nvd.nist.gov/vuln/detail/CVE-2023-51661
- https://github.com/wasmerio/wasmer/issues/4267
- https://github.com/wasmerio/wasmer/commit/4d63febf9d8b257b0531963b85df48d45d0dbf3c
- https://github.com/wasmerio/wasmer/commit/e3923612c23123025c26f982d390e34df7df030f
- https://github.com/wasmerio/wasmer
Related changes
Linked by CVE identifierNo related changes are available here.