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 bonsaidb-client

Dependencies

(22 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-lock^23.4.0out of date
 async-trait^0.10.1.83up to date
 bincode^11.3.3up to date
 bonsaidb-core=0.5.00.5.0up to date
 bonsaidb-utils=0.5.00.5.0up to date
 derive-where~1.2.01.2.7up to date
 fabruic^0.1.00.1.0up to date
 flume^0.11.00.11.1up to date
 futures^0.30.3.31up to date
 js-sys^0.30.3.72up to date
 log^0.40.4.22up to date
 once_cell^11.20.2up to date
 parking_lot^0.12.00.12.3up to date
 pot^3.0.03.0.1up to date
 serde^11.0.215up to date
 thiserror^12.0.3out of date
 tokio ⚠️^1.16.11.41.1maybe insecure
 tokio-tungstenite^0.20.00.24.0out of date
 url^2.22.5.3up to date
 wasm-bindgen^0.20.2.95up to date
 wasm-bindgen-futures^0.40.4.45up to date
 web-sys^0.30.3.72up to date

Dev dependencies

(2 total, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.93up to date
 tokio ⚠️^1.16.11.41.1maybe insecure

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);