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 mysql_async

Dependencies

(28 total, 3 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 bytes^1.41.10.1up to date
 crossbeam-queue^0.30.3.12up to date
 flate2^1.01.1.2up 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
 hdrhistogram^7.57.5.4up to date
 keyed_priority_queue^0.40.4.2up to date
 lru^0.14.00.16.0out of date
 mysql_common^0.35.40.35.4up to date
 native-tls^0.20.2.14up to date
 pem^3.03.0.5up to date
 percent-encoding^2.1.02.3.1up to date
 rand^0.90.9.2up to date
 rustls ⚠️^0.230.23.30maybe insecure
 rustls-pemfile^2.1.02.2.0up to date
 serde^11.0.219up to date
 serde_json^11.0.141up to date
 socket2^0.5.20.6.0out of date
 thiserror^22.0.12up to date
 tokio ⚠️^1.01.47.0maybe insecure
 tokio-native-tls^0.3.00.3.1up to date
 tokio-rustls^0.260.26.2up to date
 tokio-util^0.7.20.7.15up to date
 tracing^0.1.370.1.41up to date
 twox-hash^22.1.1up to date
 url^2.12.5.4up to date
 webpki-roots^0.26.11.0.2out of date

Dev dependencies

(4 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 socket2^0.5.20.6.0out of date
 tempfile^3.1.03.20.0up to date
 tokio ⚠️^1.01.47.0maybe insecure
 waker-fn^11.2.0up 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.