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 libmcaptcha

Dependencies

(13 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 actix^0.130.13.5up to date
 serde^11.0.228up to date
 serde_json^11.0.150up to date
 pretty_env_logger^0.50.5.0up to date
 log^0.40.4.33up to date
 derive_builder^0.200.20.2up to date
 derive_more^22.1.1up to date
 rand^0.90.10.2out of date
 mcaptcha_pow_sha256^0.50.6.0out of date
 redis^11.3.0up to date
 tokio ⚠️^11.52.3maybe insecure
 num_cpus^11.17.0up to date
 crossbeam-channel^0.50.5.15up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 actix-rt^22.11.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);