Security
Headlines
HeadlinesLatestCVEs

Headline

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

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

ghsa
#windows#microsoft#git
  1. GitHub Advisory Database
  2. GitHub Reviewed
  3. CVE-2024-51756

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

Low severity GitHub Reviewed Published Nov 5, 2024 in bytecodealliance/cap-std • Updated Nov 5, 2024

Package

cargo cap-async-std (Rust)

Affected versions

< 3.4.1

cargo cap-primitives (Rust)

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 bytecodealliance/cap-std#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
  • bytecodealliance/cap-std#371

References

  • GHSA-hxf5-99xg-86hw
  • bytecodealliance/cap-std#371
  • https://en.wikipedia.org/wiki/ISO/IEC_8859-1
  • https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file#naming-conventions

Published to the GitHub Advisory Database

Nov 5, 2024

ghsa: Latest News

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