CVE-2024-51756

NameCVE-2024-51756
DescriptionThe 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.
SourceCVE (at NVD; CERT, ENISA, LWN, oss-sec, fulldisc, Debian ELTS, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more)

Vulnerable and fixed packages

The table below lists information on source packages.

Source PackageReleaseVersionStatus
rust-cap-async-std (PTS)forky, sid3.4.4-1fixed
rust-cap-primitives (PTS)forky, sid3.4.4-2fixed

The information below is based on the following data on fixed versions.

PackageTypeReleaseFixed VersionUrgencyOriginDebian Bugs
rust-cap-async-stdsource(unstable)(not affected)
rust-cap-primitivessource(unstable)(not affected)

Notes

- rust-cap-primitives <not-affected> (Windows-specific)
- rust-cap-async-std <not-affected> (Windows-specific)
https://rustsec.org/advisories/RUSTSEC-2024-0445.html
https://github.com/bytecodealliance/cap-std/security/advisories/GHSA-hxf5-99xg-86hw

Search for package or bug name: Reporting problems