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 btknmle
Dependencies (12 total, 4 outdated, 1 possibly insecure)
Crate btknmle-input
Dependencies (5 total, 1 outdated, 1 possibly insecure)
Crate Required Latest Status input ^0.7
0.9.1
out of date tokio ⚠️ ^1.13
1.44.1
maybe insecure futures-core ^0.3
0.3.31
up to date libc ^0.2
0.2.171
up to date log ^0.4
0.4.27
up to date
Dev dependencies (4 total, 1 possibly insecure)
Build dependencies (1 total, 1 outdated)
Crate Required Latest Status bindgen ^0.59
0.71.1
out of date
Crate btknmle-keydb
Dependencies (6 total, 3 outdated, 1 possibly insecure)
Crate Required Latest Status tokio ⚠️ ^1.13
1.44.1
maybe insecure serde ^1.0
1.0.219
up to date toml ^0.5
0.8.20
out of date rand ^0.8
0.9.0
out of date thiserror ^1.0
2.0.12
out of date btmgmt ^0.3.0-alpha.4
0.2.5
up to date
Dev dependencies (2 total, 1 possibly insecure)
Crate Required Latest Status tokio ⚠️ ^1.13
1.44.1
maybe insecure mktemp-rs ^0.2
0.2.0
up 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