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 await-tree

Dependencies

(10 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 coarsetime^0.10.1.34up to date
 derive_builder^0.120.20.0out of date
 flexstr^0.90.9.2up to date
 indextree^44.6.1up to date
 itertools^0.110.13.0out of date
 parking_lot^0.120.12.2up to date
 pin-project^11.1.5up to date
 tokio ⚠️^11.37.0maybe insecure
 tracing^0.10.1.40up to date
 weak-table^0.3.20.3.2up to date

Dev dependencies

(3 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 criterion^0.40.5.1out of date
 futures^0.30.3.30up to date
 tokio ⚠️^11.37.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);