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 stop-token

Dependencies

(8 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-channel^1.6.12.3.1out of date
 async-global-executor^2.0.22.4.1up to date
 async-io^1.6.02.4.0out of date
 async-std^1.10.01.13.0up to date
 cfg-if^1.0.01.0.0up to date
 futures-core^0.3.170.3.31up to date
 pin-project-lite^0.2.00.2.16up to date
 tokio ⚠️^1.9.01.43.0maybe insecure

Dev dependencies

(2 total, 1 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.10.01.13.0up to date
 tokio ⚠️^1.9.01.43.0maybe insecure

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);