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

Dependencies

(22 total, 10 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.10.1.87up to date
 asynchronous-codec^0.6.10.7.0out of date
 bytes^11.10.1up to date
 futures^0.30.3.31up to date
 futures-timer^33.0.3up to date
 hex^0.40.4.3up to date
 if-watch^3.03.2.1up to date
 libp2p-core^0.38.00.43.0out of date
 libp2p-noise^0.41.00.46.0out of date
 log^0.40.4.26up to date
 multihash^0.160.19.3out of date
 prost^0.110.13.5out of date
 prost-codec^0.3.00.3.0up to date
 rand^0.80.9.0out of date
 rcgen^0.9.30.13.2out of date
 serde^1.01.0.219up to date
 stun^0.40.7.0out of date
 thiserror^12.0.12out of date
 tinytemplate^1.21.2.1up to date
 tokio ⚠️^1.191.44.1maybe insecure
 tokio-util^0.70.7.14up to date
 webrtc^0.6.00.12.0out of date

Dev dependencies

(6 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.97up to date
 env_logger^0.90.11.7out of date
 hex-literal^0.31.0.0out of date
 tokio ⚠️^1.191.44.1maybe insecure
 unsigned-varint^0.70.8.0out of 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);