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-tcp

Dependencies

(11 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-io^1.2.02.3.2out of date
 futures^0.3.80.3.30up to date
 futures-timer^3.03.0.3up to date
 if-addrs^0.7.00.12.0out of date
 if-watch^1.0.03.2.0out of date
 ipnet^2.0.02.9.0up to date
 libc^0.2.800.2.154up to date
 libp2p-core^0.32.00.41.2out of date
 log^0.4.110.4.21up to date
 socket2^0.4.00.5.7out of date
 tokio ⚠️^1.0.11.37.0maybe insecure

Dev dependencies

(3 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.6.51.12.0up to date
 env_logger^0.9.00.11.3out of date
 tokio ⚠️^1.0.11.37.0maybe 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);