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 async-speed-limit

Dependencies

(5 total, 1 possibly insecure)

CrateRequiredLatestStatus
 futures-core^0.3.10.3.31up to date
 futures-io^0.3.190.3.31up to date
 futures-timer^3.0.23.0.3up to date
 pin-project-lite^0.2.00.2.15up to date
 tokio ⚠️^11.41.1maybe insecure

Dev dependencies

(6 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 criterion^0.30.5.1out of date
 futures-executor^0.3.10.3.31up to date
 futures-util^0.3.10.3.31up to date
 rand^0.8.00.8.5up to date
 tokio ⚠️^11.41.1maybe insecure
 tokio-util^0.6.90.7.12out of 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);