GitHub Advisoryadvisory · crates.io

GHSA-hxf5-99xg-86hw cap-std doesn't fully sandbox all the Windows device filenames

LOW Published 2024-11-05 Modified 2025-12-20 Official page ↗
Aliases
CVE-2024-51756
Ecosystem
crates.io
Packages
cap-std, cap-async-std, cap-primitives
Severity
Low
CVSS vector
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
Weaknesses
CWE-22
Reviewed
2024-11-05

Affected packages

• crates.io cap-std: < 3.4.1 → fixed in 3.4.1 • crates.io cap-async-std: < 3.4.1 → fixed in 3.4.1 • crates.io cap-primitives: < 3.4.1 → fixed in 3.4.1

Description

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 • Microsoft's documentation of the special device filenames • ISO-8859-1 • https://github.com/bytecodealliance/cap-std/pull/371

Related

Alias · CVE (1)

  • CVE-2024-51756 The cap-std project is organized around the eponymous `cap-std` crate, and develops libraries to make it easy to write capability-based… vulnerability

Weakness · CWE (1)

  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory weakness

References