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 edc-connector-tui

Dependencies

(24 total, 1 possibly insecure)

CrateRequiredLatestStatus
 crossterm^0.28.10.28.1up to date
 ratatui^0.29.00.29.0up to date
 tui-textarea^0.7.00.7.0up to date
 clap^4.5.234.5.23up to date
 anyhow^1.0.941.0.95up to date
 dirs-next^2.0.02.0.0up to date
 toml^0.8.120.8.19up to date
 futures^0.3.310.3.31up to date
 tokio ⚠️^11.42.0maybe insecure
 serde^11.0.217up to date
 serde_json^11.0.134up to date
 async-trait^0.1.830.1.83up to date
 edc-connector-client^0.3.70.3.7up to date
 enum-ordinalize^4.3.04.3.0up to date
 strum^0.26.20.26.3up to date
 arboard^3.4.03.4.1up to date
 keyring^33.6.1up to date
 tui-scrollview^0.5.10.5.1up to date
 tracing-error^0.2.10.2.1up to date
 tracing-subscriber^0.3.190.3.19up to date
 directories^5.0.15.0.1up to date
 lazy_static^1.5.01.5.0up to date
 tracing^0.1.410.1.41up to date
 derive_builder^0.20.20.20.2up 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);