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 triox

Dependencies

(24 total, 7 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 config^0.130.14.0out of date
 rand^0.80.8.5up to date
 dashmap^5.35.5.3up to date
 log^0.40.4.21up to date
 env_logger^0.90.11.3out of date
 serde^11.0.200up to date
 serde_json^11.0.116up to date
 mime^0.30.3.17up to date
 actix-rt^22.9.0up to date
 actix-files^0.6.00.6.5up to date
 actix-multipart^0.4.00.6.1out of date
 actix-http^3.0.03.6.0up to date
 actix-governor^0.30.5.0out of date
 actix-web^4.0.04.5.1up to date
 actix-identity^0.4.0-beta.20.7.1out of date
 actix-service^2.02.0.2up to date
 openssl^0.10.600.10.64up to date
 sqlx^0.60.7.4out of date
 lazy_static^1.41.4.0up to date
 futures^0.30.3.30up to date
 tokio ⚠️^1.201.37.0maybe insecure
 tokio-stream^0.1.70.1.15up to date
 clap^3.24.5.4out of date
 derive_more^0.990.99.17up 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);