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


(13 total, 4 outdated, 4 possibly insecure)

 async-io^ of date
 async-std^ to date
 bytes^11.6.0up to date
 futures-io^ to date
 pin-project-lite^ to date
 quinn-proto ⚠️^ of date
 rustc-hash^ to date
 rustls ⚠️^ of date
 thiserror^ to date
 tokio ⚠️^ insecure
 tracing^ to date
 quinn-udp^ of date
 webpki ⚠️^ insecure

Dev dependencies

(12 total, 3 outdated, 1 possibly insecure)

 anyhow^ to date
 bencher^ to date
 clap^ of date
 crc^33.2.1up to date
 directories-next^22.0.0up to date
 rand^ to date
 rcgen^ of date
 rustls-pemfile^ of date
 tokio ⚠️^ insecure
 tracing-futures^ to date
 tracing-subscriber^ to date
 url^22.5.1up to date

Security Vulnerabilities

tokio: reject_remote_clients Configuration corruption


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.


Ensure that pipe_mode is set first after initializing a ServerOptions. For example:

let mut opts = ServerOptions::new();

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


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 and re-reported recently by Luke Malinowski.

webpki 0.22.1 included a partial fix and webpki 0.22.2 added further fixes.

quinn-proto: Denial of service in Quinn servers


Receiving QUIC frames containing a frame with unknown frame type could lead to a panic. Unfortunately this is issue was not found by our fuzzing infrastructure.

Thanks to the QUIC Tester research group for reporting this issue.

rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network input


If a close_notify alert is received during a handshake, complete_io does not terminate.

Callers which do not call complete_io are not affected.

rustls-tokio and rustls-ffi do not call complete_io and are not affected.

rustls::Stream and rustls::StreamOwned types use complete_io and are affected.