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 ttydash

Dependencies

(26 total, 1 possibly insecure)

CrateRequiredLatestStatus
 better-panic^0.3.00.3.0up to date
 clap^4.4.54.5.23up to date
 color-eyre^0.6.30.6.3up to date
 config^0.15.00.15.4up to date
 crossterm^0.28.10.28.1up to date
 derive_deref^1.1.11.1.1up to date
 directories^5.0.15.0.1up to date
 futures^0.3.300.3.31up to date
 human-panic^2.0.12.0.2up to date
 json5^0.4.10.4.1up to date
 lazy_static^1.5.01.5.0up to date
 libc^0.2.1580.2.169up to date
 pretty_assertions^1.4.01.4.1up to date
 ratatui^0.29.00.29.0up to date
 regex^1.10.61.11.1up to date
 serde^1.0.2081.0.217up to date
 serde_json^1.0.1251.0.134up to date
 signal-hook^0.3.170.3.17up to date
 strip-ansi-escapes^0.2.00.2.0up to date
 strum^0.26.30.26.3up to date
 tokio ⚠️^1.4.01.42.0maybe insecure
 tokio-util^0.7.110.7.13up to date
 tracing^0.1.400.1.41up to date
 tracing-error^0.2.00.2.1up to date
 tracing-subscriber^0.3.180.3.19up to date
 unicode-width^0.2.00.2.0up to date

Build dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 anyhow^1.0.861.0.95up to date
 vergen-gix^1.0.01.0.3up 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);