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 duo

Dependencies

(14 total, 6 outdated)

CrateRequiredLatestStatus
 datafusion^4246.0.0out of date
 arrow-schema^53.054.2.1out of date
 axum^0.70.8.1out of date
 clap^44.5.32up to date
 parking_lot^0.120.12.3up to date
 time^0.30.3.39up to date
 tokio^1.391.44.1up to date
 tower^0.40.5.2out of date
 rust-embed^8.58.6.0up to date
 mime_guess^22.0.5up to date
 object_store^0.110.12.0out of date
 url^2.5.22.5.4up to date
 toml^0.8.190.8.20up to date
 tower-http^0.5.20.6.2out of date

Dev dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 rstest^0.220.25.0out of date

Crate duo-api

Dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 prost^0.130.13.5up to date
 prost-types^0.130.13.5up to date

Crate duo-subscriber

Dependencies

(1 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^11.44.1maybe insecure

Dev dependencies

(3 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^11.44.1maybe insecure
 tracing-subscriber^0.30.3.19up to date
 log^0.40.4.26up 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);