{"id":"EUVD-2024-3267","revision":null,"records":[{"revision":"1c3fe4a7edb444c6af5c04dff265d8d1","observedAt":"2026-10-23T15:48:27.903+00:00","statement":{"source":"cve-program","id":"CVE-2024-51756","aliases":[],"title":"cap-std doesn't fully sandbox all the Windows device filenames","description":"The cap-std project is organized around the eponymous `cap-std` crate, and develops libraries to make it easy to write capability-based code. 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. 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. There are no known workarounds for this issue. Affected Windows users are recommended to upgrade.","state":0,"publishedAt":"2024-11-05T22:06:10.098+00:00","modifiedAt":"2024-11-06T14:39:54.948+00:00","affected":[{"ecosystem":"Vendor product","name":"cap-std","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"vendor\": \"bytecodealliance\",\n                    \"product\": \"cap-std\",\n                    \"versions\": [\n                        {\n                            \"version\": \"< 3.4.1\",\n                            \"status\": \"affected\"\n                        }\n                    ]\n                }"}],"metrics":[{"system":"CVSS 4.0","vector":"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","score":2.3,"severity":"LOW"}],"references":["https://github.com/bytecodealliance/cap-std/security/advisories/GHSA-hxf5-99xg-86hw","https://github.com/bytecodealliance/cap-std/pull/371","https://github.com/bytecodealliance/cap-std/commit/dcc3818039761331fbeacbb3a40c542b65b5ebf7","https://en.wikipedia.org/wiki/ISO/IEC_8859-1","https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file#naming-conventions"],"sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2024-51756","license":"CVE Program Terms of Use","key":"cve-program:CVE-2024-51756","identifiers":["CVE-2024-51756"]},"retained":false,"historicalAffected":[]},{"revision":"e30f893dede54d7baacf6858fe94e293","observedAt":"2026-11-09T01:09:02.378+00:00","statement":{"source":"euvd","id":"EUVD-2024-3267","aliases":["CVE-2024-51756","GHSA-hxf5-99xg-86hw"],"title":"The cap-std project is organized around the eponymous `cap-std` crate, and develops libraries to make it easy to write capability-based code. cap-std's filesystem sandbox implementation on Windows blocks access to special device filenames s…","description":"The cap-std project is organized around the eponymous `cap-std` crate, and develops libraries to make it easy to write capability-based code. 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. 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. There are no known workarounds for this issue. Affected Windows users are recommended to upgrade.","state":0,"publishedAt":null,"modifiedAt":null,"affected":[],"metrics":[{"system":"EUVD CVSS 4.0","vector":"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","score":2.3,"severity":null}],"references":["https://github.com/bytecodealliance/cap-std/security/advisories/GHSA-hxf5-99xg-86hw","https://github.com/bytecodealliance/cap-std/pull/371","https://github.com/bytecodealliance/cap-std/commit/dcc3818039761331fbeacbb3a40c542b65b5ebf7","https://en.wikipedia.org/wiki/ISO/IEC_8859-1","https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file#naming-conventions"],"sourceUrl":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2024-3267","license":"ENISA EUVD · source terms and attribution apply","enrichment":{"sourceStatus":null,"weaknesses":[],"productCriteria":[],"sourceDates":{"datePublished":"Nov 5, 2024, 10:06:10 PM","dateUpdated":"Nov 6, 2024, 2:39:54 PM"},"relatedAdvisories":[{"id":"msrc_CVE-2024-51756","title":"cap-std doesn't fully sandbox all the Windows device filenames","vulnerabilityIds":["CVE-2024-51756"]}],"note":"EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON."},"key":"euvd:EUVD-2024-3267","identifiers":["EUVD-2024-3267","CVE-2024-51756","GHSA-hxf5-99xg-86hw"]},"retained":false,"historicalAffected":[]},{"revision":"44307428d81d44b6ba94d336822dce18","observedAt":"2026-10-25T01:17:12.119+00:00","statement":{"source":"nvd","id":"CVE-2024-51756","aliases":[],"title":"The cap-std project is organized around the eponymous `cap-std` crate, and develops libraries to make it easy to write capability-based code. cap-std's filesystem sandbox implementation on Windows blocks access to special device filenames s…","description":"The cap-std project is organized around the eponymous `cap-std` crate, and develops libraries to make it easy to write capability-based code. 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. 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. There are no known workarounds for this issue. Affected Windows users are recommended to upgrade.","state":0,"publishedAt":"2024-11-05T22:15:21.817+00:00","modifiedAt":"2026-06-17T08:06:16.437+00:00","affected":[],"metrics":[{"system":"CVSS 4.0 · security-advisories@github.com · Secondary","vector":"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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","score":2.3,"severity":"LOW"}],"references":["https://en.wikipedia.org/wiki/ISO/IEC_8859-1","https://github.com/bytecodealliance/cap-std/commit/dcc3818039761331fbeacbb3a40c542b65b5ebf7","https://github.com/bytecodealliance/cap-std/pull/371","https://github.com/bytecodealliance/cap-std/security/advisories/GHSA-hxf5-99xg-86hw","https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file#naming-conventions"],"sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2024-51756","license":"NIST NVD usage terms; underlying source attribution retained","enrichment":{"sourceStatus":"Deferred","weaknesses":["CWE-22"],"productCriteria":[],"sourceDates":{"published":"2024-11-05T22:15:21.817","lastModified":"2026-06-17T08:06:16.437"},"relatedAdvisories":[],"note":"NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON."},"key":"nvd:CVE-2024-51756","identifiers":["CVE-2024-51756"]},"retained":false,"historicalAffected":[]},{"revision":"d4fb87c23dad43e49c630a168bb95c2e","observedAt":"2026-10-24T13:19:54.901+00:00","statement":{"source":"osv","id":"GHSA-hxf5-99xg-86hw","aliases":["CVE-2024-51756","RUSTSEC-2024-0445"],"title":"cap-std doesn't fully sandbox all the Windows device filenames","description":"### Impact\n\ncap-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.\n\n### Patches\n\nThe 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.\n\n### Workarounds\n\nThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade.\n\n### References\n\n - [Microsoft's documentation](https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file#naming-conventions) of the special device filenames\n - [ISO-8859-1](https://en.wikipedia.org/wiki/ISO/IEC_8859-1)\n - https://github.com/bytecodealliance/cap-std/pull/371","state":0,"publishedAt":"2024-11-05T22:19:59+00:00","modifiedAt":"2026-09-10T03:50:20.7113651+00:00","affected":[{"ecosystem":"crates.io","name":"cap-std","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"3.4.1"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"crates.io","name":"cap-async-std","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"3.4.1"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"crates.io","name":"cap-primitives","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"3.4.1"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V4","vector":"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","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"LOW"}],"references":["https://github.com/bytecodealliance/cap-std/security/advisories/GHSA-hxf5-99xg-86hw","https://nvd.nist.gov/vuln/detail/CVE-2024-51756","https://github.com/bytecodealliance/cap-std/pull/371","https://github.com/bytecodealliance/cap-std/commit/dcc3818039761331fbeacbb3a40c542b65b5ebf7","https://en.wikipedia.org/wiki/ISO/IEC_8859-1","https://github.com/bytecodealliance/cap-std","https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file#naming-conventions","https://rustsec.org/advisories/RUSTSEC-2024-0445.html"],"sourceUrl":"https://github.com/advisories/GHSA-hxf5-99xg-86hw","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-hxf5-99xg-86hw","identifiers":["GHSA-hxf5-99xg-86hw","CVE-2024-51756","RUSTSEC-2024-0445"]},"retained":false,"historicalAffected":[]},{"revision":"9914a372a6264963b2093340c3fdc0a9","observedAt":"2026-10-24T13:19:54.901+00:00","statement":{"source":"osv","id":"RUSTSEC-2024-0445","aliases":["CVE-2024-51756","GHSA-hxf5-99xg-86hw"],"title":"cap-primitives doesn't fully sandbox all the Windows device filenames","description":"## Impact\n\ncap-primitives's filesystem sandbox implementation on Windows blocks\naccess to special device filenames such as \"COM1\", \"COM2\",\n\"LPT0\", \"LPT1\", and so on, however it did not block access\nto the special device filenames which use superscript digits,\nsuch as \"COM¹\", \"COM²\", \"LPT⁰\", \"LPT¹\", and so on. Untrusted\nfilesystem paths could bypass the sandbox and access devices\nthrough those special device filenames with superscript\ndigits, and through them provide access peripheral devices\nconnected to the computer, or network resources mapped to\nthose devices. This can include modems, printers, network\nprinters, and any other device connected to a serial or\nparallel port, including emulated USB serial ports.\n\n## Patches\n\nThe bug is fixed in #371, which is published in\ncap-primitives 3.4.1, cap-std 3.4.1, and cap-async-std 3.4.1.\n\n## Workarounds\n\nThere are no known workarounds for this issue.\nAffected Windows users are recommended to upgrade.","state":0,"publishedAt":"2024-11-05T12:00:00+00:00","modifiedAt":"2026-10-12T18:00:13.0047117+00:00","affected":[{"ecosystem":"crates.io","name":"cap-primitives","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0.0.0-0"},{"kind":"fixed","version":"3.4.1"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V4","vector":"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","score":null,"severity":null}],"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"],"sourceUrl":"https://osv.dev/vulnerability/RUSTSEC-2024-0445","license":"OSV · upstream source license applies","key":"osv:RUSTSEC-2024-0445","identifiers":["RUSTSEC-2024-0445","CVE-2024-51756","GHSA-hxf5-99xg-86hw"]},"retained":false,"historicalAffected":[]}],"coverage":[{"source":"cisa-kev:global","scope":"Complete CISA KEV catalog; all vendors. Missing entries do not establish absence of exploitation.","generation":"2026-11-10T10:21:23.1769119+00:00","complete":true,"records":1773,"lastAttemptAt":"2026-11-10T10:21:23.1769119+00:00","lastSuccessAt":"2026-11-10T10:21:23.4268898+00:00","error":null,"lastVerifiedAt":"2026-11-10T10:21:23.4268987+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"cve-program","scope":"Official CVE Program baseline and cumulative hourly delta; all vendors, published and rejected records","generation":"cve-8859cf40d4337e24bd2f258cc7778fbad01bb24c79d057aaf34cf1dfc6f8917d-8bdcdeeb414e06ff50ed637d818ac25d52680d19f71fc0ebe3f4c4b3f836ed38","complete":true,"records":421927,"lastAttemptAt":"2026-11-10T10:21:22.8157744+00:00","lastSuccessAt":"2026-11-10T09:21:38.1064889+00:00","error":null,"lastVerifiedAt":"2026-11-10T10:21:22.8157744+00:00","snapshotPublishedAt":"2026-11-10T09:20:43+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"euvd","scope":"Rolling EUVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global EUVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-2e6a476534094233b48f2f0b6da5cf35","complete":true,"records":13689,"lastAttemptAt":"2026-11-10T10:21:50.2500014+00:00","lastSuccessAt":"2026-11-10T06:05:35.03+00:00","error":null,"lastVerifiedAt":"2026-11-10T06:05:35.03+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13742,"expectedIdentifiers":13742,"failedIdentifiers":0},{"source":"first-epss:nuget","scope":"FIRST EPSS for explicit CVE aliases in the collected public NuGet archive. Not a global EPSS backfill.","generation":"2026-11-10T10:21:23.1769119+00:00","complete":true,"records":1096,"lastAttemptAt":"2026-11-10T10:21:23.1769119+00:00","lastSuccessAt":"2026-11-10T10:21:23.4276529+00:00","error":null,"lastVerifiedAt":"2026-11-10T10:21:23.4276532+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"nvd","scope":"Rolling NVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global NVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-b0b0499af228434598651aa5d221386e","complete":false,"records":13695,"lastAttemptAt":"2026-11-10T10:21:49.6403901+00:00","lastSuccessAt":"2026-11-10T10:21:49.637+00:00","error":"100 identifier lookups failed; latest failures include request timeout. Other identifiers were checked independently.","lastVerifiedAt":"2026-11-10T10:21:49.637+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13642,"expectedIdentifiers":13742,"failedIdentifiers":100},{"source":"osv:Go","scope":"Complete OSV Go ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"go-cdffb4589856378aa42e8d1bd4a6c74e27a180d8160bf764c44715ef760f0a62","complete":true,"records":9932,"lastAttemptAt":"2026-11-10T10:21:23.1241572+00:00","lastSuccessAt":"2026-11-10T00:04:19.8260565+00:00","error":null,"lastVerifiedAt":"2026-11-10T10:21:23.1241572+00:00","snapshotPublishedAt":"2026-11-09T23:48:01+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:NuGet","scope":"Complete OSV NuGet ecosystem archive, including GitHub Advisory Database records; NuGet version matching only","generation":"nuget-26503967ae4379db8f374089589d6e03fb15bd31f820c9e992aaf93840c2236c","complete":true,"records":1971,"lastAttemptAt":"2026-11-10T10:21:22.8858542+00:00","lastSuccessAt":"2026-11-09T21:02:20.472473+00:00","error":null,"lastVerifiedAt":"2026-11-10T10:21:22.8858542+00:00","snapshotPublishedAt":"2026-11-09T20:18:18+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:crates.io","scope":"Complete OSV crates.io ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"crates.io-94169eec81ea3989aa551092397ff34ae53c104b4a6ce646e1524452e4ab2a39","complete":true,"records":3065,"lastAttemptAt":"2026-11-10T10:21:23.1397622+00:00","lastSuccessAt":"2026-11-10T08:04:45.5923716+00:00","error":null,"lastVerifiedAt":"2026-11-10T10:21:23.1397622+00:00","snapshotPublishedAt":"2026-11-10T06:48:01+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:npm","scope":"Complete OSV npm ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"npm-4331051b0b2d4ccdbdca3aa196b0be3818a465064a4b18dde4cf39c2250eb490","complete":true,"records":231599,"lastAttemptAt":"2026-11-10T10:21:23.0142877+00:00","lastSuccessAt":"2026-11-10T08:04:37.1757322+00:00","error":null,"lastVerifiedAt":"2026-11-10T10:21:23.0142877+00:00","snapshotPublishedAt":"2026-11-10T07:33:02+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null}]}