cap-std
Capability-oriented version of the Rust standard library
View on Github
Activity
- Latest release
- 3w ago
- Total releases
- 94
- Cadence
- ~13 days
- Last 12 months
- 6
Reach
- Stars
- 816
Details
- License
- Apache-2.0 WITH LLVM-exception OR Apache-2.0 OR MIT
- First release
- Jun 25, 2020
| Version | Released | |
|---|---|---|
3.4.6
patch
|
3.4.6
patch
Dependencies (6)
Changelog
Compare changes
|
|
4.0.3
patch
|
4.0.3
patch
Dependencies (6)
Changelog
Compare changes
|
|
4.0.2
unknown
|
4.0.2
unknown
Dependencies (6)
Changelog
Compare changes
|
|
4.0.1
unknown
yanked
|
4.0.1
unknown
yanked
Dependencies (6)
Changelog
Compare changes
|
|
4.0.0
unknown
|
4.0.0
unknown
Dependencies (6)
Changelog
Compare changes
|
|
3.4.5
unknown
|
3.4.5
unknown
Dependencies (6)
Changelog
Compare changes
|
|
3.4.4
unknown
|
3.4.4
unknown
Dependencies (6)
Changelog
Compare changes
|
|
3.4.3
unknown
|
3.4.3
unknown
Dependencies (6)
Changelog
Compare changes
|
|
3.4.2
unknown
|
3.4.2
unknown
Dependencies (6)
Changelog
Compare changes
|
|
2.0.2
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
2.0.2
unknown
Dependencies (6)
Changelog
Compare changes
|
|
3.4.1
unknown
|
3.4.1
unknown
Dependencies (6)
Changelog
Compare changes
|
|
3.4.0
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
3.4.0
unknown
Dependencies (6)
Changelog
Compare changes
|
|
3.3.0
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
3.3.0
unknown
Dependencies (6)
Changelog
Compare changes
|
|
3.2.0
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
3.2.0
unknown
Dependencies (6)
Changelog
Compare changes
|
|
3.1.0
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
3.1.0
unknown
Dependencies (6)
Changelog
Compare changes
|
|
3.0.0
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
3.0.0
unknown
Dependencies (6)
Changelog
Compare changes
|
|
2.0.1
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
2.0.1
unknown
Dependencies (6)
Changelog
Compare changes
|
|
2.0.0
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
2.0.0
unknown
Dependencies (6)
Changelog
Compare changes
|
|
1.0.16
unknown
yanked
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
1.0.16
unknown
yanked
Dependencies (6)
Changelog
Compare changes
|
|
1.0.15
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
1.0.15
unknown
Dependencies (6)
Changelog
Compare changes
|
|
1.0.14
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
1.0.14
unknown
Dependencies (6)
Changelog
Compare changes
|
|
1.0.13
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
1.0.13
unknown
Dependencies (6)
Changelog
Compare changes
|
|
1.0.12
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
1.0.12
unknown
Dependencies (6)
Changelog
Compare changes
|
|
1.0.11
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
1.0.11
unknown
Dependencies (6)
Changelog
Compare changes
|
|
1.0.10
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
1.0.10
unknown
Dependencies (6)
Changelog
Compare changes
|
|
1.0.9
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
1.0.9
unknown
Dependencies (6)
Changelog
Compare changes
|
|
1.0.8
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
1.0.8
unknown
Dependencies (6)
Changelog
Compare changes
|
|
1.0.7
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
1.0.7
unknown
Dependencies (7)
Changelog
Compare changes
|
|
1.0.6
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
1.0.6
unknown
Dependencies (7)
Changelog
Compare changes
|
|
1.0.5
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
1.0.5
unknown
Dependencies (7)
Changelog
Compare changes
|
|
1.0.4
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
1.0.4
unknown
Dependencies (7)
Changelog
Compare changes
|
|
1.0.3
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
1.0.3
unknown
Dependencies (7)
Changelog
Compare changes
|
|
1.0.2
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
1.0.2
unknown
Dependencies (7)
Changelog
Compare changes
|
|
1.0.1
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
1.0.1
unknown
Dependencies (7)
Changelog
Compare changes
|
|
1.0.0
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
1.0.0
unknown
Dependencies (7)
Changelog
Compare changes
|
|
0.26.1
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.26.1
unknown
Dependencies (7)
Changelog
Compare changes
|
|
1.0.0-rc2
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
1.0.0-rc2
unknown
Dependencies (7)
Changelog
Compare changes
|
|
0.26.0
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.26.0
unknown
Dependencies (7)
Changelog
Compare changes
|
|
0.26.0-patch2
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.26.0-patch2
unknown
Dependencies (7)
Changelog
Compare changes
|
|
0.25.3
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.25.3
unknown
Dependencies (7)
Changelog
Compare changes
|
|
0.26.0-patch1
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.26.0-patch1
unknown
Dependencies (7)
Changelog
Compare changes
|
|
0.26.0-patch0
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.26.0-patch0
unknown
Dependencies (7)
Changelog
Compare changes
|
|
1.0.0-rc1
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
1.0.0-rc1
unknown
Dependencies (7)
Changelog
Compare changes
|
|
0.25.2
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.25.2
unknown
Dependencies (7)
Changelog
Compare changes
|
|
0.25.1
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.25.1
unknown
Dependencies (7)
Changelog
Compare changes
|
|
0.25.0
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.25.0
unknown
Dependencies (7)
Changelog
Compare changes
|
|
0.24.4
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.24.4
unknown
Dependencies (7)
Changelog
Compare changes
|
|
0.24.3
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.24.3
unknown
Dependencies (7)
Changelog
Compare changes
|
|
0.24.2
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.24.2
unknown
Dependencies (7)
Changelog
Compare changes
|
|
0.24.1
unknown
1 CVE
CVE-2024-51756
GHSA-hxf5-99xg-86hw
RUSTSEC-2024-0445
Nov 05, 2024
cap-std doesn't fully sandbox all the Windows device filenames
Low
Network
Low
Low
None
Impactcap-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. PatchesThe 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. WorkaroundsThere are no known workarounds for this issue. Affected Windows users are recommended to upgrade. References
Fixed in
3.4.1
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.24.1
unknown
Dependencies (7)
Changelog
Compare changes
|