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 btmgmt

Dependencies

(9 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 futures-core^0.30.3.30up to date
 futures-sink^0.30.3.30up to date
 futures-util^0.30.3.30up to date
 futures-channel^0.30.3.30up to date
 tokio ⚠️^1.141.40.0maybe insecure
 socket2^0.40.5.7out of date
 libc^0.20.2.158up to date
 thiserror^1.01.0.63up to date
 log^0.40.4.22up to date

Dev dependencies

(4 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 futures^0.30.3.30up to date
 tokio ⚠️^1.141.40.0maybe insecure
 pretty_env_logger^0.40.5.0out of date
 tokio-test^0.4.20.4.4up to date

Crate btmgmt-packet

Dependencies

(7 total, 3 outdated)

CrateRequiredLatestStatus
 bdaddr^0.2.0-alpha.40.1.2up to date
 thiserror^1.01.0.63up to date
 bitflags^1.32.6.0out of date
 uuid^0.81.10.0out of date
 getset^0.10.1.3up to date
 derive-new^0.50.7.0out of date
 smallvec^1.71.13.2up to date

Crate btmgmt-cli

Dependencies

(5 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 clap^3.0.0-rc.04.5.17out of date
 anyhow^1.01.0.89up to date
 tokio ⚠️^1.131.40.0maybe insecure
 pretty_env_logger^0.40.5.0out of date
 futures^0.30.3.30up to date

Crate btmgmt-packet-macros

Dependencies

(3 total, 1 outdated)

CrateRequiredLatestStatus
 proc-macro2^1.01.0.86up to date
 quote^1.01.0.37up to date
 syn^1.02.0.77out of date

Crate btmgmt-packet-helper

Dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 thiserror^1.01.0.63up to date

Dev dependencies

(2 total, 1 outdated)

CrateRequiredLatestStatus
 bitflags^1.22.6.0out of date
 trybuild^1.01.0.99up 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);