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

Dependencies

(2 total, 2 possibly insecure)

CrateRequiredLatestStatus
 rustls ⚠️^0.23.150.23.20maybe insecure
 tokio ⚠️^1.01.42.0maybe insecure

Dev dependencies

(6 total, 1 possibly insecure)

CrateRequiredLatestStatus
 argh^0.1.10.1.12up to date
 futures-util^0.3.10.3.31up to date
 lazy_static^1.11.5.0up to date
 rcgen^0.130.13.1up to date
 tokio ⚠️^1.01.42.0maybe insecure
 webpki-roots^0.260.26.7up 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 network-reachable panic in `Acceptor::accept`

RUSTSEC-2024-0399

A bug introduced in rustls 0.23.13 leads to a panic if the received TLS ClientHello is fragmented. Only servers that use rustls::server::Acceptor::accept() are affected.

Servers that use tokio-rustls's LazyConfigAcceptor API are affected.

Servers that use tokio-rustls's TlsAcceptor API are not affected.

Servers that use rustls-ffi's rustls_acceptor_accept API are affected.