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 h2

Dependencies

(11 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^11.10.1up to date
 fnv^1.0.51.0.7up to date
 futures-core^0.30.3.31up to date
 futures-sink^0.30.3.31up to date
 futures-util^0.30.3.31up to date
 http^0.21.3.1out of date
 indexmap^1.5.22.10.0out of date
 slab^0.4.20.4.10up to date
 tokio ⚠️^11.45.1maybe insecure
 tokio-util^0.60.7.15out of date
 tracing^0.1.210.1.41up to date

Dev dependencies

(12 total, 9 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 env_logger^0.5.30.11.8out of date
 hex^0.2.00.4.3out of date
 quickcheck^0.4.11.0.3out of date
 rand^0.3.150.9.1out of date
 rustls ⚠️^0.190.23.28out of date
 serde^1.0.01.0.219up to date
 serde_json^1.0.01.0.140up to date
 tokio ⚠️^11.45.1maybe insecure
 tokio-rustls^0.220.26.2out of date
 walkdir^1.0.02.5.0out of date
 webpki ⚠️^0.210.22.4out of date
 webpki-roots^0.211.0.1out of 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.

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

RUSTSEC-2024-0336

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.