CVE-2024-51756 json
cap-std doesn't fully sandbox all the Windows device filenames
published 2y ago modified 30d ago also GHSA-hxf5-99xg-86hw , RUSTSEC-2024-0445 , EUVD-2024-3267
- cvss
- 2.3
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 48%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- crates.io cap-std 3.4.1
- crates.io cap-async-std 3.4.1
- crates.io cap-primitives 3.4.1
- github.com/bytecodealliance/cap-std@dcc3818 commit
- github.com/bytecodealliance/cap-std#371 pull request
Is CVE-2024-51756 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.58% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 2.3 | CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N |
| CNA | 4.0 | 2.3 | CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | cap-std | <3.4.1 |
3.4.1 |
| crates.io | cap-async-std | <3.4.1 |
3.4.1 |
| crates.io | cap-primitives | <3.4.1 >=0.0.0-0, <3.4.1 |
3.4.1 |
Affected products
- bytecodealliance cap-std
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/bytecodealliance/cap-std/pull/371
web
-
github.com
/bytecodealliance/cap-std/commit/dcc3818039761331fbeacbb3a40c542b65b5ebf7
web
-
github.com
/bytecodealliance/cap-std/security/advisories/GHSA-hxf5-99xg-86hw
web
-
en.wikipedia.org
/wiki/ISO/IEC_8859-1
web
-
learn.microsoft.com
/en-us/windows/win32/fileio/naming-a-file#naming-conventions
web
-
nvd.nist.gov
/vuln/detail/CVE-2024-51756
advisory, web
-
github.com
/bytecodealliance/cap-std
package
-
rustsec.org
/advisories/RUSTSEC-2024-0445.html
web, advisory
-
crates.io
/crates/cap-primitives
package
Sources
- CVE List CVE-2024-51756
- GitHub Advisory GHSA-hxf5-99xg-86hw
- NVD CVE-2024-51756
- OSV RUSTSEC-2024-0445
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.