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

Dependencies

(13 total, 6 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-io^1.3.12.4.0out of date
 data-encoding^2.3.22.8.0up to date
 futures^0.3.130.3.31up to date
 if-watch^3.0.03.2.1up to date
 libp2p-core^0.38.00.43.0out of date
 libp2p-swarm^0.41.00.46.0out of date
 log^0.4.140.4.26up to date
 rand^0.8.30.9.0out of date
 smallvec^1.6.11.14.0up to date
 socket2^0.4.00.5.8out of date
 tokio ⚠️^1.191.44.1maybe insecure
 trust-dns-proto^0.22.00.23.2out of date
 void^1.0.21.0.2up to date

Dev dependencies

(3 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.9.01.13.0up to date
 env_logger^0.9.00.11.7out of date
 tokio ⚠️^1.191.44.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);