RUSTSEC-2024-0445

See a problem?
Please try reporting it to the source first.

Source

https://rustsec.org/advisories/RUSTSEC-2024-0445

Import Source

https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2024-0445.json

JSON Data

https://api.test.osv.dev/v1/vulns/RUSTSEC-2024-0445

Aliases

Published

2024-11-05T12:00:00Z

Modified

2025-12-19T21:26:00.174038Z

Severity

2.3 (Low) CVSS_V4 - 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 CVSS Calculator

Summary

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

Details

Impact

cap-primitives'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 #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.

Database specific

{
    "license": "CC-BY-4.0"
}

References

Affected packages

crates.io / cap-primitives

Package

Name: cap-primitives; View open source insights on deps.dev
Purl: pkg:cargo/cap-primitives

Affected ranges

Type: SEMVER
Events: Introduced

0.0.0-0

Fixed

3.4.1

Ecosystem specific

{
    "affects": {
        "functions": [],
        "arch": [],
        "os": [
            "windows"
        ]
    },
    "affected_functions": null
}