Advisory

GHSA-4mq4-7rw3-vm5j

Also known as: CVE-2023-51661

Summary

Wasmer filesystem sandbox not enforced

Details

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2023-12-13 13:32 UTC
Modified
2026-09-10 03:49 UTC

Affected packages and fixes

wasmer-cli

crates.io · All systems

Affected

  • introduced 3.0.0, fixed 4.2.4 (semver)

Fixed versions

4.2.4

Fix

  • Fixed version 4.2.4
    cargo update -p wasmer-cli --precise 4.2.4

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences