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-core

Dependencies

(25 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 actionable^0.2.00.2.0up to date
 anyhow^11.0.93up to date
 arc-bytes^0.3.30.3.5up to date
 async-trait^0.10.1.83up to date
 blake3^1.3.11.5.4up to date
 bonsaidb-macros=0.5.00.5.0up to date
 bytecount^0.6.30.6.8up to date
 circulate^0.5.00.5.0up to date
 derive-where~1.2.01.2.7up to date
 futures^0.30.3.31up to date
 itertools^0.110.13.0out of date
 num-traits^0.20.2.19up to date
 num_cpus^1.13.11.16.0up to date
 ordered-varint^2.0.02.0.0up to date
 pot^3.0.03.0.1up to date
 rand^0.8.50.8.5up to date
 serde^11.0.215up to date
 sha2^0.100.10.8up to date
 thiserror^12.0.3out of date
 tinyvec^1.5.11.8.0up to date
 tokio ⚠️^1.16.11.41.1maybe insecure
 transmog^0.1.00.1.0up to date
 transmog-pot^0.3.00.3.0up to date
 uuid^1.3.01.11.0up to date
 zeroize^11.8.1up to date

Dev dependencies

(7 total, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.93up to date
 futures^0.30.3.31up to date
 hex-literal^0.4.10.4.1up to date
 num-derive^0.4.00.4.2up to date
 num_cpus^11.16.0up to date
 tokio ⚠️^1.16.11.41.1maybe insecure
 transmog-bincode^0.10.1.0up 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);