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 bdk-cli

Dependencies

(27 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bdk_wallet^3.1.03.1.0up to date
 clap^4.64.6.5up to date
 clap_complete^4.64.6.8up to date
 dirs^6.0.06.0.0up to date
 env_logger^0.11.100.11.11up to date
 log^0.40.4.33up to date
 serde_json^1.01.0.151up to date
 thiserror^2.0.182.0.19up to date
 tokio ⚠️^11.53.1maybe insecure
 cli-table^0.5.00.5.0up to date
 tracing^0.1.440.1.44up to date
 tracing-subscriber^0.3.200.3.23up to date
 toml^1.1.01.1.4+spec-1.1.0up to date
 serde^1.01.0.229up to date
 tap^1.0.11.0.1up to date
 bdk_bitcoind_rpc^0.22.00.22.0up to date
 bdk_electrum^0.24.00.24.0up to date
 bdk_esplora^0.22.20.22.2up to date
 bdk_kyoto^0.17.00.17.0up to date
 bdk_redb^0.2.00.2.0up to date
 bdk_sp^0.2.00.2.0up to date
 shlex^1.3.02.0.1out of date
 payjoin^0.25.00.25.0up to date
 reqwest^0.13.20.13.4up to date
 url^2.5.82.5.8up to date
 bdk_message_signer^0.2.00.2.0up to date
 bitcoin-payment-instructions^0.7.00.7.1up to date

Dev dependencies

(4 total, all up-to-date)

CrateRequiredLatestStatus
 predicates^3.03.1.4up to date
 tempfile^3.83.27.0up to date
 assert_cmd^2.2.22.2.2up to date
 bdk_testenv^0.13.10.13.1up 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);