This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.

Crate goosefs-sdk

Dependencies

(26 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 arc-swap^11.9.2up to date
 async-trait^0.10.1.92up to date
 bytes^1.11.11.12.1up to date
 dashmap^66.2.1up to date
 fastrand^22.5.0up to date
 futures^0.30.3.34up to date
 hostname^0.40.4.2up to date
 io-uring^0.70.7.14up to date
 itoa^11.0.18up to date
 libc^0.20.2.189up to date
 lru^0.18.10.18.2up to date
 memmap2^0.90.9.11up to date
 moka^0.120.12.16up to date
 prost^0.14.10.14.4up to date
 prost-types^0.14.10.14.4up to date
 rand^0.9.10.10.2out of date
 reqwest^0.120.13.4out of date
 serde^11.0.229up to date
 thiserror^22.0.20up to date
 tokio ⚠️^1.231.53.1maybe insecure
 tokio-stream^0.1.140.1.19up to date
 tonic^0.140.14.6up to date
 tonic-prost^0.140.14.6up to date
 tracing^0.10.1.44up to date
 uuid^1.21.24.1up to date
 xxhash-rust^0.8.150.8.18up to date

Dev dependencies

(2 total, 1 possibly insecure)

CrateRequiredLatestStatus
 criterion^0.80.8.2up to date
 tokio ⚠️^1.231.53.1maybe insecure

Security Vulnerabilities

tokio: reject_remote_clients Configuration corruption

RUSTSEC-2023-0001

On Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.

This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.

The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.

Workarounds

Ensure that pipe_mode is set first after initializing a ServerOptions. For example:

let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);