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 clientele

Dependencies

(17 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 argfile^0.20.2.1up to date
 camino^1.11.2.1up to date
 clap^4.54.5.49up to date
 dirs^6.06.0.0up to date
 dogma^0.10.1.11up to date
 dotenvy^0.150.15.7up to date
 duration-str^0.150.17.0out of date
 error-stack^0.50.6.0out of date
 getenv^0.10.1.2up to date
 gofer^0.1.60.1.8up to date
 known-errors^0.10.1.1up to date
 serde^11.0.228up to date
 serde_json^11.0.145up to date
 tokio ⚠️^11.48.0maybe insecure
 tracing-core^0.10.1.34up to date
 ubyte^0.100.10.4up to date
 wild^22.2.1up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 temp-dir^0.10.1.16up 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);