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 libp2p-swarm

Dependencies

(17 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.6.21.13.0up to date
 either^1.6.01.15.0up to date
 fnv^1.01.0.7up to date
 futures^0.3.10.3.31up to date
 futures-timer^3.0.23.0.3up to date
 getrandom^0.2.30.3.1out of date
 instant^0.1.110.1.13up to date
 libp2p-core^0.38.00.43.0out of date
 libp2p-swarm-derive^0.31.00.35.0out of date
 log^0.40.4.26up to date
 pin-project^1.0.01.1.10up to date
 rand^0.80.9.0out of date
 smallvec^1.6.11.14.0up to date
 thiserror^1.02.0.12out of date
 tokio ⚠️^1.151.44.1maybe insecure
 void^11.0.2up to date
 wasm-bindgen-futures^0.4.330.4.50up to date

Dev dependencies

(5 total, 1 outdated)

CrateRequiredLatestStatus
 async-std^1.6.21.13.0up to date
 either^1.6.01.15.0up to date
 env_logger^0.90.11.7out of date
 futures^0.3.10.3.31up to date
 void^11.0.2up 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);