CVE-2024-51756 – cap-async-std

Package

Manager: cargo
Name: cap-async-std
Vulnerable Version: >=0 <3.4.1

Severity

Level: Low

CVSS v3.1: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:P/RL:O/RC:C

CVSS v4.0: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

EPSS: 0.00516 pctl0.65698

Details

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 - [Microsoft's documentation](https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file#naming-conventions) of the special device filenames - [ISO-8859-1](https://en.wikipedia.org/wiki/ISO/IEC_8859-1) - https://github.com/bytecodealliance/cap-std/pull/371

Metadata

Created: 2024-11-05T22:19:59Z
Modified: 2024-11-06T14:28:24Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/11/GHSA-hxf5-99xg-86hw/GHSA-hxf5-99xg-86hw.json
CWE IDs: ["CWE-22"]
Alternative ID: GHSA-hxf5-99xg-86hw
Finding: F063
Auto approve: 1