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

(13 total, 3 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 async-io^1.61.13.0up to date
 async-std^1.111.12.0up to date
 bytes^11.5.0up to date
 futures-io^0.3.190.3.28up to date
 pin-project-lite^0.20.2.13up to date
 quinn-proto^0.9.40.10.5out of date
 rustc-hash^1.11.1.0up to date
 rustls^0.20.30.21.7out of date
 thiserror^1.0.211.0.48up to date
 tokio ⚠️^1.13.01.32.0maybe insecure
 tracing^0.1.100.1.37up to date
 quinn-udp^0.30.4.1out of date
 webpki ⚠️^0.220.22.1maybe insecure

Dev dependencies

(12 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.221.0.75up to date
 bencher^0.1.50.1.5up to date
 clap^3.24.4.4out of date
 crc^33.0.1up to date
 directories-next^22.0.0up to date
 rand^0.80.8.5up to date
 rcgen^0.10.00.11.1out of date
 rustls-pemfile^1.0.01.0.3up to date
 tokio ⚠️^1.0.11.32.0maybe insecure
 tracing-futures^0.2.00.2.5up to date
 tracing-subscriber^0.3.00.3.17up to date
 url^22.4.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 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);

webpki: webpki: CPU denial of service in certificate path building

RUSTSEC-2023-0052

When this crate is given a pathological certificate chain to validate, it will spend CPU time exponential with the number of candidate certificates at each step of path building.

Both TLS clients and TLS servers that accept client certificate are affected.

This was previously reported in https://github.com/briansmith/webpki/issues/69 and re-reported recently by Luke Malinowski.