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-ucx

Dependencies

(10 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 crossbeam^0.80.8.4up to date
 derivative^2.2.02.2.0up to date
 futures^0.30.3.31up to date
 futures-lite^1.112.6.0out of date
 lazy_static^1.41.5.0up to date
 log^0.40.4.27up to date
 socket2^0.40.5.10out of date
 thiserror^1.02.0.12out of date
 tokio ⚠️^1.01.45.1maybe insecure
 ucx1-sys^0.10.1.0up to date

Dev dependencies

(5 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 env_logger^0.90.11.8out of date
 test-log^0.20.2.18up to date
 tokio ⚠️^1.01.45.1maybe insecure
 tracing^0.10.1.41up to date
 tracing-subscriber^0.2.170.3.19out 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);