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 chromium-crypto

Dependencies

(20 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 TinyUFO^0.50.6.0out of date
 aead^0.50.5.2up to date
 aes^0.80.8.4up to date
 aes-gcm^0.100.10.3up to date
 base64^0.220.22.1up to date
 block-padding^0.3.30.3.3up to date
 cbc^0.10.1.2up to date
 cfg-if^11.0.1up to date
 chacha20poly1305^0.100.10.1up to date
 keyring^33.6.3up to date
 pbkdf2^0.120.12.2up to date
 secret-service^55.0.0up to date
 serde^11.0.219up to date
 serde_json^11.0.142up to date
 sha1^0.100.10.6up to date
 snafu^0.80.8.6up to date
 tokio ⚠️^11.47.1maybe insecure
 tracing^0.10.1.41up to date
 windows^0.610.61.3up to date
 winnow^0.7.110.7.12up 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);