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 msql-srv

Dependencies

(5 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 nom^77.1.3up to date
 mysql_common^0.31.00.32.4out of date
 byteorder^11.5.0up to date
 chrono^0.4.230.4.38up to date
 rustls ⚠️^0.22.10.23.12out of date

Dev dependencies

(9 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 postgres^0.19.10.19.8up to date
 mysql^2425.0.1out of date
 mysql_async^0.33.00.34.1out of date
 slab^0.4.20.4.9up to date
 tokio ⚠️^1.15.01.39.1maybe insecure
 futures^0.3.00.3.30up to date
 rcgen^0.8.140.13.1out of date
 tempfile^3.3.03.10.1up to date
 native-tls^0.2.80.2.12up 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.