VYPR
← All advisories
Low severityOSV Advisory· Published Nov 5, 2024· Updated Apr 15, 2026

CVE-2024-51756

CVE-2024-51756

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.

Affected packages

Versions sourced from the GitHub Security Advisory.

PackageAffected versionsPatched versions
cap-stdcrates.io
< 3.4.13.4.1
cap-async-stdcrates.io
< 3.4.13.4.1
cap-primitivescrates.io
< 3.4.13.4.1

Affected products

1

Patches

2
c461c0799f83
https://github.com/bytecodealliance/cap-stdvia osv
commit
dcc381803976

Add missing reserved file names (#371)

https://github.com/bytecodealliance/cap-stdnathaniel-danielNov 5, 2024via ghsa
commit
1 file changed · +4 −2
  • cap-primitives/src/windows/fs/open_impl.rs+4 −2 modified
    @@ -10,12 +10,14 @@ pub(crate) fn open_impl(
 ) -> io::Result<fs::File> {
     // Windows reserves several special device paths. Disallow opening any
     // of them.
+    // See: https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file#naming-conventions
     if let Some(stem) = path.file_stem() {
         if let Some(stemstr) = stem.to_str() {
             match stemstr.to_uppercase().as_str() {
                 "CON" | "PRN" | "AUX" | "NUL" | "COM0" | "COM1" | "COM2" | "COM3" | "COM4"
-                | "COM5" | "COM6" | "COM7" | "COM8" | "COM9" | "LPT0" | "LPT1" | "LPT2"
-                | "LPT3" | "LPT4" | "LPT5" | "LPT6" | "LPT7" | "LPT8" | "LPT9" => {
+                | "COM5" | "COM6" | "COM7" | "COM8" | "COM9" | "COM¹" | "COM²" | "COM³"
+                | "LPT0" | "LPT1" | "LPT2" | "LPT3" | "LPT4" | "LPT5" | "LPT6" | "LPT7"
+                | "LPT8" | "LPT9" | "LPT¹" | "LPT²" | "LPT³" => {
                     return Err(io::Error::from_raw_os_error(ERROR_FILE_NOT_FOUND as i32));
                 }
                 _ => {}

Vulnerability mechanics

Generated by null/stub on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.

References

8

News mentions

0

No linked articles in our index yet.