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 rukaidata_bot

Dependencies

(3 total, 1 possibly insecure)

CrateRequiredLatestStatus
 poise^0.6.10.6.1up to date
 time^0.3.70.3.39up to date
 tokio ⚠️^1.151.44.0maybe insecure

Crate rukaidata_website

Dependencies

(22 total, 3 outdated)

CrateRequiredLatestStatus
 brawllib_rs^0.270.27.0up to date
 serde_derive^11.0.219up to date
 serde^11.0.219up to date
 serde_json^11.0.140up to date
 env_logger^0.110.11.7up to date
 log^0.40.4.26up to date
 handlebars=4.2.26.3.1out of date
 rayon^11.10.0up to date
 minifier^0.30.3.5up to date
 sha2^0.100.10.8up to date
 futures^0.30.3.31up to date
 subprocess^0.2.70.2.9up to date
 bincode^12.0.1out of date
 wasm-bindgen-cli-support^0.2.780.2.100up to date
 flate2^1.0.281.1.0up to date
 tokio^1.35.11.44.0up to date
 axum^0.7.30.8.1out of date
 tower-http^0.6.00.6.2up to date
 clap^4.4.124.5.32up to date
 base64^0.22.10.22.1up to date
 anstyle^1.0.71.0.10up to date
 anyhow^11.0.97up 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);