Low severity · published Nov 5, 2024
CVE-2024-51756
cap-std doesn't fully sandbox all the Windows device filenames
2.3
CVSS
0.6%
EPSS
No
On KEV
Description
The cap-std project is organized around the eponymous `cap-std` crate, and develops libraries to make it easy to write capability-based code. 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. The bug is fixed in #371, which is published in cap-primitives 3.4.1, cap-std 3.4.1, and cap-async-std 3.4.1. There are no known workarounds for this issue. Affected Windows users are recommended to upgrade.
Exploitation
Is it being used?
Exploit prediction (EPSS)0.6% · higher than 48% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
CA
cap-std · bytecodealliance
< 3.4.1 · source: vendor
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2024-51756
CVE.org
https://www.cve.org/CVERecord?id=CVE-2024-51756
en.wikipedia.org
https://en.wikipedia.org/wiki/ISO/IEC_8859-1
github.com
https://github.com/bytecodealliance/cap-std/commit/dcc3818039761331fbeacbb3a40c542b65b5ebf7
github.com
https://github.com/bytecodealliance/cap-std/pull/371
github.com
https://github.com/bytecodealliance/cap-std/security/advisories/GHSA-hxf5-99xg-86hw
learn.microsoft.com
https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file#naming-conventions
