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 chromiumoxide_fetcher

Dependencies

(11 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.102up to date
 async-std^1.51.13.2up to date
 directories^66.0.0up to date
 reqwest^0.120.13.2out of date
 serde^11.0.228up to date
 surf^2.32.3.2up to date
 thiserror^12.0.18out of date
 tokio ⚠️^11.51.0maybe insecure
 tracing^0.10.1.44up to date
 windows-version^0.10.1.7up to date
 zip^0.68.5.0out of date

Dev dependencies

(2 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 reqwest^0.120.13.2out of date
 tokio ⚠️^11.51.0maybe 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);