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 ipfs-api-prelude

Dependencies

(18 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.10.1.81up to date
 bytes^11.6.1up to date
 cfg-if^11.0.0up to date
 common-multipart-rfc7578^0.60.6.0up to date
 dirs^45.0.1out of date
 futures^0.30.3.30up to date
 http^0.21.1.0out of date
 multiaddr^0.170.18.1out of date
 multibase^0.90.9.1up to date
 serde^11.0.204up to date
 serde_json^11.0.120up to date
 serde_urlencoded^0.70.7.1up to date
 thiserror^11.0.63up to date
 tokio ⚠️^11.38.1maybe insecure
 tokio-util^0.70.7.11up to date
 tracing^0.10.1.40up to date
 typed-builder^0.100.19.1out of date
 walkdir^2.32.5.0up to date

Dev dependencies

(3 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^11.38.1maybe insecure
 tokio-stream^0.10.1.15up to date
 tracing-subscriber^0.30.3.18up to date

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);