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_extra

Dependencies

(13 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 base64^0.220.22.1up to date
 etag^44.0.0up to date
 futures-util^0.30.3.31up to date
 hyper^11.5.0up to date
 pin-project^11.1.7up to date
 salvo_core^0.70.00.74.0out of date
 serde^11.0.214up to date
 serde_json^11.0.132up to date
 tokio ⚠️^11.41.0maybe insecure
 tokio-tungstenite^0.230.24.0out of date
 tokio-util^0.70.7.12up to date
 tracing^0.10.1.40up to date
 ulid^11.1.3up to date

Dev dependencies

(5 total, 1 outdated)

CrateRequiredLatestStatus
 http-body-util^0.10.1.2up to date
 salvo_core^0.70.00.74.0out of date
 time^0.30.3.36up to date
 tokio-stream^0.10.1.16up to date
 tracing-test^0.2.10.2.5up 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);