Vulnerability GHSA-hxf5-99xg-86hw

Low Risk
LOW RISK
CVSS Score: 3.0
Score Range: < 4.0
Low severity vulnerabilities (CVSS < 4.0). Hygiene issues that can accumulate but pose lower immediate risk.
1 year ago
November 05, 2024 at 10:19 PM UTC
cap-std doesn't fully sandbox all the Windows device filenames
0.0.0 - 0.25.3 and 0.26.0 - 3.4.0
0.0.0 - 0.25.3 and 0.26.0 - 3.4.0

Summary

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

Details

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

Timeline

Published
1 year ago
November 05, 2024 at 10:19 PM UTC
Fixed (3.4.1)
1 year ago
November 05, 2024 at 04:21 PM UTC
Fixed (3.4.1)
1 year ago
November 05, 2024 at 04:21 PM UTC
Fixed (3.4.1)
1 year ago
November 05, 2024 at 04:22 PM UTC
Last Modified
1 month ago
September 10, 2026 at 03:50 AM UTC