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)
Dev dependencies (4 total, 1 outdated, 1 possibly insecure)
Crate btmgmt-packet Dependencies (7 total, 4 outdated)
Crate btmgmt-cli Dependencies (5 total, 2 outdated, 1 possibly insecure)
Crate btmgmt-packet-macros Dependencies (3 total, 1 outdated)
Crate Required Latest Status proc-macro2 ^1.01.0.103up to date quote ^1.01.0.42up to date syn ^1.02.0.111out of date
Crate btmgmt-packet-helper Dependencies (1 total, 1 outdated)
Crate Required Latest Status thiserror ^1.02.0.17out of date
Dev dependencies (2 total, 1 outdated)
Crate Required Latest Status bitflags ^1.22.10.0out of date trybuild ^1.01.0.114up to date
Security Vulnerabilities tokio: reject_remote_clients Configuration corruptionRUSTSEC-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);
Patched
>=1.18.4, <1.19.0
>=1.20.3, <1.21.0
>=1.23.1