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 quinn

Dependencies

(11 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^11.3.0up to date
 futures-channel^0.3.110.3.25up to date
 futures-util^0.3.110.3.25up to date
 fxhash^0.2.10.2.1up to date
 quinn-proto^0.8.40.9.2out of date
 rustls^0.20.30.20.8up to date
 thiserror^1.0.211.0.38up to date
 tokio ⚠️^1.0.11.24.2maybe insecure
 tracing^0.1.100.1.37up to date
 quinn-udp^0.1.00.3.2out of date
 webpki^0.220.22.0up to date

Dev dependencies

(13 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.221.0.68up to date
 bencher^0.1.50.1.5up to date
 crc^23.0.0out of date
 directories-next^22.0.0up to date
 futures-util^0.3.110.3.25up to date
 rand^0.80.8.5up to date
 rcgen^0.80.10.0out of date
 rustls-pemfile^0.2.11.0.2out of date
 structopt^0.3.00.3.26up to date
 tokio ⚠️^1.0.11.24.2maybe insecure
 tracing-futures^0.2.00.2.5up to date
 tracing-subscriber^0.3.00.3.16up to date
 url^22.3.1up 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 overriden 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);