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 boh

Dependencies

(27 total, 12 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.82up to date
 async-scoped^0.70.9.0out of date
 base64^0.210.22.1out of date
 bytes^1.01.6.0up to date
 camino^1.11.1.6up to date
 clap^4.04.5.4up to date
 futures-util^0.30.3.30up to date
 http^0.21.1.0out of date
 memmap2^0.50.9.4out of date
 nu-ansi-term^0.470.50.0out of date
 number_prefix^0.40.4.0up to date
 openssl ⚠️^0.100.10.64maybe insecure
 rayon^1.51.10.0up to date
 reqwest^0.110.12.4out of date
 ring^0.160.17.8out of date
 serde^1.01.0.200up to date
 serde_json^1.01.0.116up to date
 serde_yaml^0.90.9.34+deprecatedup to date
 symbolic-common^10.012.8.0out of date
 symbolic-debuginfo^10.012.8.0out of date
 tame-gcs^0.120.13.0out of date
 tame-oauth^0.80.10.0out of date
 time^0.30.3.36up to date
 tokio ⚠️^1.01.37.0maybe insecure
 url^2.22.5.0up to date
 walkdir^2.32.5.0up to date
 zstd^0.120.13.1out 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);

openssl: `openssl` `X509VerifyParamRef::set_host` buffer over-read

RUSTSEC-2023-0044

When this function was passed an empty string, openssl would attempt to call strlen on it, reading arbitrary memory until it reached a NUL byte.