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 mobc

Dependencies

(9 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 actix-rt^12.9.0out of date
 async-std^1.01.12.0up to date
 async-trait^0.10.1.80up to date
 futures-channel^0.30.3.30up to date
 futures-core^0.30.3.30up to date
 futures-timer^3.0.23.0.3up to date
 futures-util^0.30.3.30up to date
 log^0.40.4.21up to date
 tokio ⚠️^11.37.0maybe insecure

Dev dependencies

(6 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 actix-rt^22.9.0up to date
 actix-web^34.5.1out of date
 async-std^1.01.12.0up to date
 env_logger^0.80.11.3out of date
 tide^0.160.16.0up to date
 tokio ⚠️^11.37.0maybe 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);