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 salvo-proxy

Dependencies

(10 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 fastrand^22.1.1up to date
 futures-util^0.30.3.31up to date
 hyper^11.5.0up to date
 hyper-rustls^0.270.27.3up to date
 hyper-util^0.1.20.1.10up to date
 percent-encoding^22.3.1up to date
 reqwest^0.12.10.12.9up to date
 salvo_core^0.70.00.74.0out of date
 tokio ⚠️^11.41.0maybe insecure
 tracing^0.10.1.40up to date

Dev dependencies

(2 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 salvo_core^0.70.00.74.0out of date
 tokio ⚠️^11.41.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);