// For flags

CVE-2024-51756

cap-std doesn't fully sandbox all the Windows device filenames

Severity Score

2.3
*CVSS v4

Exploit Likelihood

*EPSS

Affected Versions

*CPE

Public Exploits

0
*Multiple Sources

Exploited in Wild

-
*KEV

Decision

Track
*SSVC
Descriptions

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.

El proyecto cap-std está organizado en torno al cajón homónimo `cap-std`, y desarrolla librerías para facilitar la escritura de código basado en capacidades. La implementación del sandbox del sistema de archivos de cap-std en Windows bloquea el acceso a nombres de archivos de dispositivos especiales como "COM1", "COM2", "LPT0", "LPT1", etc., sin embargo, no bloquea el acceso a los nombres de archivos de dispositivos especiales que utilizan dígitos en superíndice, como "COM¹", "COM²", "LPT?", "LPT¹", etc. Las rutas del sistema de archivos no confiables podrían eludir el sandbox y acceder a los dispositivos a través de esos nombres de archivos de dispositivos especiales con dígitos en superíndice, y a través de ellos proporcionar acceso a dispositivos periféricos conectados a la computadora o recursos de red asignados a esos dispositivos. Esto puede incluir módems, impresoras, impresoras de red y cualquier otro dispositivo conectado a un puerto serial o paralelo, incluidos los puertos seriales USB emulados. El error se corrigió en el n.° 371, que se publicó en cap-primitives 3.4.1, cap-std 3.4.1 y cap-async-std 3.4.1. No se conocen workarounds para este problema. Se recomienda a los usuarios de Windows afectados que actualicen.

*Credits: N/A
CVSS Scores
Attack Vector
Network
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
Low
User Interaction
None
System
Vulnerable | Subsequent
Confidentiality
Low
None
Integrity
Low
None
Availability
Low
None
* Common Vulnerability Scoring System
SSVC
  • Decision:Track
Exploitation
None
Automatable
No
Tech. Impact
Partial
* Organization's Worst-case Scenario
Timeline
  • 2024-10-31 CVE Reserved
  • 2024-11-05 CVE Published
  • 2024-11-06 CVE Updated
  • 2024-11-06 EPSS Updated
  • ---------- Exploited in Wild
  • ---------- KEV Due Date
  • ---------- First Exploit
CWE
  • CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CAPEC
Affected Vendors, Products, and Versions
Vendor Product Version Other Status
Vendor Product Version Other Status <-- --> Vendor Product Version Other Status
Bytecodealliance
Search vendor "Bytecodealliance"
 Cap-std
Search vendor "Bytecodealliance" for product "Cap-std"
 < 3.4.1
Search vendor "Bytecodealliance" for product "Cap-std" and version " < 3.4.1"
en
Affected