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

(22 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bdk_wallet^2.1.02.3.0up to date
 clap^4.54.5.60up to date
 dirs^6.0.06.0.0up to date
 env_logger^0.11.60.11.9up to date
 log^0.40.4.29up to date
 serde_json^1.01.0.149up to date
 thiserror^2.0.112.0.18up to date
 tokio ⚠️^11.49.0maybe insecure
 cli-table^0.5.00.5.0up to date
 tracing^0.1.410.1.44up to date
 tracing-subscriber^0.3.200.3.22up to date
 toml^0.8.231.0.3+spec-1.1.0out of date
 serde^1.01.0.228up to date
 bdk_bitcoind_rpc^0.21.00.22.0out of date
 bdk_electrum^0.23.00.23.2up to date
 bdk_esplora^0.22.10.22.1up to date
 bdk_kyoto^0.15.10.15.4up to date
 bdk_redb^0.1.00.1.1up to date
 shlex^1.3.01.3.0up to date
 payjoin^1.0.0-rc.10.24.0up to date
 reqwest^0.12.230.13.2out of date
 url^2.5.42.5.8up 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);