wasmtime
Affected
- introduced
0, fixed24.0.2(semver)
Fixed versions
24.0.2
Fix
- Fixed version
24.0.2cargo update -p wasmtime --precise 24.0.2
Advisory
Also known as: CVE-2024-51745, RUSTSEC-2024-0438
Wasmtime doesn't fully sandbox all the Windows device filenames
Impact
Wasmtime's filesystem sandbox implementation on Windows blocks access to special device filenames such as "COM1", "COM2", "LPT0", "LPT1", and so on, however it did not block access to the special device filenames which use superscript digits, such as "COM¹", "COM²", "LPT⁰", "LPT¹", and so on. Untrusted Wasm programs that are given access to any filesystem directory could bypass the sandbox and access devices through those special device filenames with superscript digits, and through them gain access peripheral devices connected to the computer, or network resources mapped to those devices. This can include modems, printers, network printers, and any other device connected to a serial or parallel port, including emulated USB serial ports.
Patches
Patch releases for Wasmtime have been issued as 24.0.2, 25.0.3, and 26.0.1. Users of Wasmtime 23.0.x and prior are recommended to upgrade to one of these patched versions.
Workarounds
There are no known workarounds for this issue. Affected Windows users are recommended to upgrade.
References
Low Basis: The source's own band: LOW
0, fixed 24.0.2 (semver)24.0.2
24.0.2cargo update -p wasmtime --precise 24.0.225.0.0, fixed 25.0.3 (semver)25.0.3
25.0.3cargo update -p wasmtime --precise 25.0.326.0.0, fixed 26.0.1 (semver)26.0.1
26.0.1cargo update -p wasmtime --precise 26.0.1Fix 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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0