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 hyper-rustls

Dependencies

(12 total, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 futures-util^0.30.3.30up to date
 http^11.1.0up to date
 hyper^11.3.1up to date
 hyper-util^0.10.1.5up to date
 log^0.4.40.4.21up to date
 rustls-pki-types^11.7.0up to date
 rustls ⚠️^0.220.23.9out of date
 rustls-native-certs^0.70.7.0up to date
 tokio ⚠️^1.01.38.0maybe insecure
 tokio-rustls^0.250.26.0out of date
 tower-service^0.30.3.2up to date
 webpki-roots^0.260.26.2up to date

Dev dependencies

(5 total, 1 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 http-body-util^0.10.1.2up to date
 hyper-util^0.10.1.5up to date
 rustls ⚠️^0.220.23.9out of date
 rustls-pemfile^22.1.2up to date
 tokio ⚠️^1.01.38.0maybe insecure

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);

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.