cap-std
Affected
- introduced
0, fixed3.4.1(semver)
Fixed versions
3.4.1
Fix
- Fixed version
3.4.1cargo update -p cap-std --precise 3.4.1
Advisory
Also known as: CVE-2024-51756, RUSTSEC-2024-0445
cap-std doesn't fully sandbox all the Windows device filenames
Impact
cap-std'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 filesystem paths could bypass the sandbox and access devices through those special device filenames with superscript digits, and through them provide 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
The bug is fixed in https://github.com/bytecodealliance/cap-std/pull/371, which is published in cap-primitives 3.4.1, cap-std 3.4.1, and cap-async-std 3.4.1.
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 3.4.1 (semver)3.4.1
3.4.1cargo update -p cap-std --precise 3.4.10, fixed 3.4.1 (semver)3.4.1
3.4.1cargo update -p cap-async-std --precise 3.4.10, fixed 3.4.1 (semver)3.4.1
3.4.1cargo update -p cap-primitives --precise 3.4.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