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 cyper-axum

Dependencies

(16 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-tungstenite^0.34.00.35.0out of date
 axum^0.8.10.8.9up to date
 axum-core^0.5.00.5.6up to date
 base64^0.220.23.1out of date
 compio^0.19.00.19.2up to date
 compio-log^0.2.00.2.1up to date
 cyper-core^0.9.00.9.0up to date
 futures-util^0.3.300.3.34up to date
 hyper^1.4.11.11.1up to date
 hyper-util^0.1.200.1.20up to date
 send_wrapper^0.60.6.0up to date
 sha1^0.110.11.0up to date
 socket2^0.60.6.5up to date
 tokio ⚠️^11.53.1maybe insecure
 tower^0.5.10.5.3up to date
 tower-service^0.3.20.3.3up to date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 compio^0.19.00.19.2up to date
 futures-channel^0.3.290.3.34up 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);