cap-primitives doesn't fully sandbox all the Windows device filenames
## 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.
- Products
- cap-primitives
- Affected versions
- Not specified
- Fixed versions
- 3.4.1
- CVEs
- CVE-2024-51756
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 30 Oct 2026, 08:44 UTC · Revision 1
Source evidence
cap-primitives doesn't fully sandbox all the Windows device filenames
core-osv · Original sourcePublished 5 Nov 2024, 12:00 UTC
## 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.
osv:RUSTSEC-2024-0445
cap-primitives
Fixed versions: 3.4.1
Complete source record
{
"id": "56e5ffba3d453b4cacd4ee865c8d0b6a1e4bc59833a14d0abfb5f531a4739873",
"url": "https://osv.dev/vulnerability/RUSTSEC-2024-0445",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "cap-primitives doesn't fully sandbox all the Windows device filenames",
"summary": "## 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.",
"evidence": "osv:RUSTSEC-2024-0445",
"products": [
{
"name": {
"value": "cap-primitives",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "3.4.1",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": []
}
],
"severity": "low",
"structured": {
"id": "RUSTSEC-2024-0445",
"aliases": [
"CVE-2024-51756",
"GHSA-hxf5-99xg-86hw",
"RUSTSEC-2024-0445"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "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"
}
],
"affected": [
{
"ranges": [
{
"type": "SEMVER",
"events": [
{
"introduced": "0.0.0-0"
},
{
"fixed": "3.4.1"
}
]
}
],
"package": {
"name": "cap-primitives",
"purl": "pkg:cargo/cap-primitives",
"ecosystem": "crates.io"
},
"database_specific": {
"cvss": "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",
"source": "https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2024-0445.json",
"categories": [],
"informational": null
},
"ecosystem_specific": {
"affects": {
"os": [
"windows"
],
"arch": [],
"functions": []
},
"affected_functions": null
}
}
],
"modified": "2026-10-12T18:00:13.004711734Z",
"provider": "osv",
"references": [
"https://crates.io/crates/cap-primitives",
"https://rustsec.org/advisories/RUSTSEC-2024-0445.html",
"https://github.com/bytecodealliance/cap-std/pull/371",
"https://nvd.nist.gov/vuln/detail/CVE-2024-51756"
],
"provider_metadata": {
"license": "CC-BY-4.0"
}
},
"related_cves": [
{
"value": "CVE-2024-51756",
"evidence": "/aliases"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 306433,
"published_at": "2024-11-05T12:00:00+00:00"
}