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 scuffle-signal

Dependencies

(5 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.98up to date
 scuffle-bootstrap^0.0.20.1.2out of date
 scuffle-context^0.0.20.1.2out of date
 scuffle-workspace-hack^0.1.00.1.0up to date
 tokio ⚠️^11.45.0maybe insecure

Dev dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 futures^0.30.3.31up to date
 libc^0.20.2.172up to date
 tokio^1.41.11.45.0up 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);