Advisory Database
  • Advisories
  • Dependency Scanning
  1. cargo
  2. ›
  3. cap-async-std
  4. ›
  5. CVE-2024-51756

CVE-2024-51756: cap-std doesn't fully sandbox all the Windows device filenames

November 5, 2024 (updated November 6, 2024)

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.

References

  • en.wikipedia.org/wiki/ISO/IEC_8859-1
  • github.com/advisories/GHSA-hxf5-99xg-86hw
  • github.com/bytecodealliance/cap-std
  • github.com/bytecodealliance/cap-std/commit/dcc3818039761331fbeacbb3a40c542b65b5ebf7
  • github.com/bytecodealliance/cap-std/pull/371
  • github.com/bytecodealliance/cap-std/security/advisories/GHSA-hxf5-99xg-86hw
  • learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file
  • nvd.nist.gov/vuln/detail/CVE-2024-51756

Code Behaviors & Features

Detect and mitigate CVE-2024-51756 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions before 3.4.1

Fixed versions

  • 3.4.1

Solution

Upgrade to version 3.4.1 or above.

Weakness

  • CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Source file

cargo/cap-async-std/CVE-2024-51756.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Wed, 14 May 2025 12:14:38 +0000.