CVE-2024-51756

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 i...

gpiocdev (>=0.4.3, <=0.7.0), gpiocdev-embedded-hal (0.1.0) +1 more potentially affected by CVE-2024-51756 via cap-std (3.0.0)

cap-std CARGO version 3.0.0 is affected by a known vulnerability. The following packages have a transitive dependency on cap-std and may be impacted: - gpiocdev =0.4.3, =0.16.0, =0.16.3 Source cves: CVE-2024-51756 Source advisory: OSV:GHSA-HXF5-99XG-86HW...

gpiocdev (>=0.4.3, <=0.7.0), gpiocdev-embedded-hal (0.1.0) +1 more potentially affected by CVE-2024-51756 via cap-std (3.0.0)

cap-std CARGO version 3.0.0 is affected by a known vulnerability. The following packages have a transitive dependency on cap-std and may be impacted: - gpiocdev =0.4.3, =0.16.0, =0.16.3 Source cves: CVE-2024-51756 Source advisory: GHSA-HXF5-99XG-86HW...

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 o...

GHSA-HXF5-99XG-86HW 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 o...

CVE-2024-51756

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 i...

CVE-2024-51756 cap-std doesn't fully sandbox all the Windows device filenames

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 i...

CVE-2024-51756

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...

CVE-2024-51756

The CVE affects cap-std’s Windows filesystem sandbox, where access to special device filenames with superscript digits (e.g., COM¹, LPT⁰) was not blocked, allowing untrusted paths to bypass the sandbox and reach peripheral devices or network-shared resources mapped to those devices. Root cause: t...

CVE-2024-51756 cap-std doesn't fully sandbox all the Windows device filenames

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 i...

CVE-2024-51756 cap-std doesn't fully sandbox all the Windows device filenames

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 i...

cap-std path traversal vulnerability

cap-std is a feature-based version of the Rust Standard Library open-sourced by the Bytecode Alliance. A path traversal vulnerability exists in versions of cap-std prior to 3.4.1, which stems from a failure of the file system sandbox implementation on Windows to prevent access to special device...

CVE-2024-51756: Improper Limitation of a Pathname to a Restricted Directory

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 i...

candid-extractor (>=0.1.0, <=0.1.2), purewasm (0.1.0) +8 more potentially affected by CVE-2024-47763 via wasmtime (12.0.2)

wasmtime CARGO version 12.0.2 is affected by a known vulnerability. The following packages have a transitive dependency on wasmtime and may be impacted: - candid-extractor =0.1.0, =12.0.0, =12.0.0, =0.1.2, =0.3.0, =12.0.0, =12.0.0, =12.0.0, =12.0.2 Source cves: CVE-2024-47763 Source advisory:...

candid-extractor (>=0.1.0, <=0.1.2), purewasm (0.1.0) +8 more potentially affected by CVE-2024-47763 via wasmtime (12.0.2)

wasmtime CARGO version 12.0.2 is affected by a known vulnerability. The following packages have a transitive dependency on wasmtime and may be impacted: - candid-extractor =0.1.0, =12.0.0, =12.0.0, =0.1.2, =0.3.0, =12.0.0, =12.0.0, =12.0.0, =12.0.2 Source cves: CVE-2024-47763 Source advisory:...