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 kaspa-miner

Dependencies

(28 total, 8 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 tonic^0.80.12.3out of date
 tokio ⚠️^1.171.44.0maybe insecure
 prost^0.110.13.5out of date
 futures-util^0.30.3.31up to date
 tokio-stream^0.10.1.17up to date
 once_cell^11.21.0up to date
 num_cpus^11.16.0up to date
 rand^0.80.9.0out of date
 blake2b_simd^1.0.01.0.3up to date
 clap^3.04.5.32out of date
 log^0.40.4.26up to date
 env_logger^0.90.11.7out of date
 keccak^0.10.1.5up to date
 parking_lot^0.120.12.3up to date
 shuttle^0.2.00.8.0out of date
 libloading^0.70.8.6out of date
 tokio-util^0.7.00.7.13up to date
 serde_json^1.01.0.140up to date
 serde_repr^0.10.1.20up to date
 serde^1.01.0.219up to date
 futures^0.3.210.3.31up to date
 bytes^1.1.01.10.1up to date
 async-trait^0.10.1.87up to date
 num^0.40.4.3up to date
 nix^0.250.29.0out of date
 hex^0.40.4.3up to date
 semver^1.01.0.26up to date
 time^0.30.3.39up to date

Build dependencies

(3 total, 1 outdated)

CrateRequiredLatestStatus
 tonic-build^0.80.12.3out of date
 cc^11.2.16up to date
 time^0.30.3.39up 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);