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 eprofiler-tui

Dependencies

(6 total, 1 possibly insecure)

CrateRequiredLatestStatus
 better-panic^0.30.3.0up to date
 clap^4.5.574.5.58up to date
 ratatui^0.300.30.0up to date
 thiserror^22.0.18up to date
 tokio ⚠️^11.49.0maybe insecure
 tonic^0.140.14.4up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 tokio-stream^0.1.180.1.18up to date

Crate eprofiler-proto

Dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 prost^0.140.14.3up to date
 tonic^0.140.14.4up to date
 tonic-prost^0.140.14.4up to date

Build dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 tonic-prost-build^0.140.14.4up 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);