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 mail-send

Dependencies

(13 total, 7 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 base64^0.220.22.1up to date
 gethostname^0.41.0.2out of date
 mail-auth^0.40.7.1out of date
 mail-builder^0.30.4.3out of date
 mail-parser^0.90.11.0out of date
 md5^0.7.00.8.0out of date
 rand^0.8.50.9.1out of date
 rustls ⚠️^0.230.23.29maybe insecure
 rustls-pki-types^11.12.0up to date
 smtp-proto^0.10.1.6up to date
 tokio ⚠️^1.231.46.1maybe insecure
 tokio-rustls^0.260.26.2up to date
 webpki-roots^0.261.0.1out of date

Dev dependencies

(2 total, 1 possibly insecure)

CrateRequiredLatestStatus
 env_logger^0.11.00.11.8up to date
 tokio ⚠️^1.161.46.1maybe 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 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.