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 tokio-tungstenite

Dependencies

(10 total, 5 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 futures-util^0.3.280.3.30up to date
 log^0.4.170.4.22up to date
 native-tls^0.2.110.2.12up to date
 rustls ⚠️^0.21.60.23.11out of date
 rustls-native-certs^0.6.20.7.1out of date
 tokio ⚠️^1.0.01.38.1maybe insecure
 tokio-native-tls^0.3.10.3.1up to date
 tokio-rustls^0.24.10.26.0out of date
 tungstenite^0.20.10.23.0out of date
 webpki-roots^0.25.20.26.3out of date

Dev dependencies

(5 total, 2 outdated)

CrateRequiredLatestStatus
 env_logger^0.10.00.11.3out of date
 futures-channel^0.3.280.3.30up to date
 hyper^0.14.251.4.1out of date
 tokio^1.27.01.38.1up to date
 url^2.3.12.5.2up 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);

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.