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, 3 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 bytes^11.6.0up to date
 futures-channel^0.3.110.3.30up to date
 futures-util^0.3.110.3.30up to date
 fxhash^0.2.10.2.1up to date
 quinn-proto ⚠️^0.8.40.10.6out of date
 rustls^0.20.30.23.4out of date
 thiserror^1.0.211.0.58up to date
 tokio ⚠️^1.0.11.36.0maybe insecure
 tracing^0.1.100.1.40up to date
 quinn-udp^0.1.00.4.1out of date
 webpki ⚠️^0.220.22.4maybe insecure

Dev dependencies

(13 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.221.0.81up to date
 bencher^0.1.50.1.5up to date
 crc^23.0.1out of date
 directories-next^22.0.0up to date
 futures-util^0.3.110.3.30up to date
 rand^0.80.8.5up to date
 rcgen^0.80.13.0out of date
 rustls-pemfile^0.2.12.1.1out of date
 structopt^0.3.00.3.26up to date
 tokio ⚠️^1.0.11.36.0maybe insecure
 tracing-futures^0.2.00.2.5up to date
 tracing-subscriber^0.3.00.3.18up to date
 url^22.5.0up 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.

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

quinn-proto: Denial of service in Quinn servers

RUSTSEC-2023-0063

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.