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, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 futures-core^0.30.3.31up to date
 futures-sink^0.30.3.31up to date
 futures-util^0.30.3.31up to date
 futures-channel^0.30.3.31up to date
 tokio ⚠️^1.141.44.1maybe insecure
 socket2^0.40.5.9out of date
 libc^0.20.2.171up to date
 thiserror^1.02.0.12out of date
 log^0.40.4.27up to date

Dev dependencies

(4 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 futures^0.30.3.31up to date
 tokio ⚠️^1.141.44.1maybe 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, 4 outdated)

CrateRequiredLatestStatus
 bdaddr^0.2.0-alpha.40.1.2up to date
 thiserror^1.02.0.12out of date
 bitflags^1.32.9.0out of date
 uuid^0.81.16.0out of date
 getset^0.10.1.5up to date
 derive-new^0.50.7.0out of date
 smallvec^1.71.14.0up to date

Crate btmgmt-cli

Dependencies

(5 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 clap^3.0.0-rc.04.5.34out of date
 anyhow^1.01.0.97up to date
 tokio ⚠️^1.131.44.1maybe insecure
 pretty_env_logger^0.40.5.0out of date
 futures^0.30.3.31up to date

Crate btmgmt-packet-macros

Dependencies

(3 total, 1 outdated)

CrateRequiredLatestStatus
 proc-macro2^1.01.0.94up to date
 quote^1.01.0.40up to date
 syn^1.02.0.100out of date

Crate btmgmt-packet-helper

Dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 thiserror^1.02.0.12out of date

Dev dependencies

(2 total, 1 outdated)

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