16 matches found
AZL-111068 CVE-2026-115392 affecting package rpm-ostree 2024.4-11
Wasmtime before 24.0.13, 25.0.0 before 36.0.14, 37.0.0 before 46.0.3, and 47.0.0 before 47.0.4 allows a filesystem sandbox escape in wasmtime-wasi because its cap-std dependency mishandles symlinks with trailing slashes on macOS and Linux kernels lacking openat2. A guest with write access to any...
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...
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...
cap-dir-ext (>=0.3.0, <=0.6.0), cap-directories (>=0.1.0, <=2.0.2) +59 more potentially affected by CVE-2024-51756 via cap-std (>=0.1.0, <=3.0.0)
cap-std CARGO version =0.1.0, =0.3.0, =0.1.0, =0.7.0, =1.0.11, =0.1.1, =0.1.0, =0.3.0, =0.1.1, =0.1.0, =0.5.3-0, =0.4.0-pre, =0.4.0-pre, =0.0.1, =0.0.1-alpha, =0.4.3, =0.7.0 and more Source cves: CVE-2024-51756 Source advisory: OSV: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...
cap-dir-ext (>=0.3.0, <=0.6.0), cap-directories (>=0.1.0, <=2.0.2) +59 more potentially affected by CVE-2024-51756 via cap-std (>=0.1.0, <=3.0.0)
cap-std CARGO version =0.1.0, =0.3.0, =0.1.0, =0.7.0, =1.0.11, =0.1.1, =0.1.0, =0.3.0, =0.1.1, =0.1.0, =0.5.3-0, =0.4.0-pre, =0.4.0-pre, =0.0.1, =0.0.1-alpha, =0.4.3, =0.7.0 and more Source cves: CVE-2024-51756 Source advisory: GHSA-HXF5-99XG-86HW...
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 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 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 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: 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...
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...
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:...