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 actix-hash

Dependencies

(18 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 actix-http^33.7.0up to date
 actix-web^44.6.0up to date
 actix-web-lab^0.190.20.2out of date
 blake2^0.100.10.6up to date
 blake3^1.31.5.1up to date
 digest^0.100.10.7up to date
 futures-core^0.3.170.3.30up to date
 futures-util^0.3.170.3.30up to date
 local-channel^0.10.1.5up to date
 md4^0.100.10.2up to date
 md-5^0.100.10.6up to date
 pin-project-lite^0.20.2.14up to date
 sha1^0.100.10.6up to date
 sha2^0.100.10.8up to date
 sha3^0.100.10.8up to date
 subtle^22.5.0up to date
 tokio ⚠️^1.18.51.37.0maybe insecure
 tracing^0.1.300.1.40up 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);