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 tame-index

Dependencies

(20 total, 7 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^1.41.10.1up to date
 camino^1.11.1.10up to date
 crossbeam-channel^0.50.5.15up to date
 gix^0.550.72.1out of date
 home^0.50.5.11up to date
 http^0.21.3.1out of date
 libc^0.20.2.174up to date
 memchr^2.52.7.5up to date
 rayon^1.71.10.0up to date
 reqwest^0.110.12.21out of date
 semver^1.01.0.26up to date
 serde^1.01.0.219up to date
 serde_json^1.01.0.140up to date
 sha2^0.100.10.9up to date
 smol_str^0.2.00.3.2out of date
 thiserror^1.02.0.12out of date
 tokio ⚠️^1.01.45.1maybe insecure
 toml^0.80.8.23up to date
 twox-hash^1.62.1.1out of date
 windows-targets^0.48.50.53.2out of date

Dev dependencies

(4 total, 2 outdated)

CrateRequiredLatestStatus
 cargo_metadata^0.180.20.0out of date
 rayon^1.71.10.0up to date
 tempfile^3.63.20.0up to date
 tiny-bench^0.30.4.0out of 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);