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

(15 total, 4 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 tonic^0.100.12.3out of date
 tokio ⚠️^11.42.0maybe insecure
 prost^0.120.13.4out of date
 tokio-stream^0.10.1.17up to date
 num_cpus^11.16.0up to date
 rand^0.80.8.5up to date
 blake2b_simd^1.0.01.0.2up to date
 clap^44.5.23up to date
 log^0.40.4.22up to date
 env_logger^0.100.11.6out of date
 arc-swap^1.6.01.7.1up to date
 keccak^0.10.1.5up to date
 parking_lot^0.120.12.3up to date
 shuttle^0.60.8.0out of date
 chrono ⚠️^0.40.4.39maybe insecure

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 sha3^0.100.10.8up to date

Build dependencies

(2 total, 1 outdated)

CrateRequiredLatestStatus
 tonic-build^0.100.12.3out of date
 cc^11.2.5up to date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.

Workarounds

No workarounds are known.

References

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);