11 matches found
async-std-resolver (>=0.25.0-alpha.1, <=0.25.0-alpha.5), ezk-sip-ua (>=0.5.0, <=0.7.1) +5 more potentially affected by unknown CVE via hickory-proto (>=0.25.0-alpha.1, <=0.25.0-alpha.5)
hickory-proto CARGO version =0.25.0-alpha.1, =0.25.0-alpha.1, =0.5.0, =0.25.0-alpha.1, =0.25.0-alpha.5 - hickory-resolver 0.25.0-alpha.1 - hickory-server 0.25.0-alpha.1 - shadowsocks 1.22.0 Source cves: unknown CVE Source advisory: OSV:RUSTSEC-2026-0118...
a2 (>=0.5.0-alpha.1, <=0.5.0), a_chat (0.1.0) +2619 more potentially affected by unknown CVE via async-std (>=0.99.4, <=1.13.2)
async-std CARGO version =0.99.4, =0.5.0-alpha.1, =0.1.0, =0.3.1, =0.1.0, =0.1.0, =0.7.0, =0.3.0, =0.1.1, =0.1.0, =0.1.0, =0.1.0, =0.1.3, =0.1.4 and more Source cves: unknown CVE Source advisory: OSV:RUSTSEC-2025-0052...
RUSTSEC-2025-0052 async-std has been discontinued
The async-std has been discontinued. Alternatives: - smol...
async-std has been discontinued
The async-std has been discontinued. Alternatives: - smol...
PT-2025-36674
The async-std has been discontinued. Alternatives: - smol...
RUSTSEC-2025-0036 surf is unmaintained
The developer has indicated that the crate is unmaintained. The last release is over three years old from 2021, the crate depends on the deprecated async-std crate and on a very old version of rustls for TLS support. Possible alternatives - reqwest - ureq...
PT-2025-21911 · Crates.Io · Surf
The developer has indicated that the crate is unmaintained. The last release is over three years old from 2021, the crate depends on the deprecated async-std crate and on a very old version of rustls for TLS support. Possible alternatives - reqwest - ureq...
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...
RUSTSEC-2024-0445 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¹", a...
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...