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 hyper-staticfile

Dependencies

(11 total, 1 possibly insecure)

CrateRequiredLatestStatus
 futures-util^0.3.10.3.31up to date
 http^1.0.01.1.0up to date
 http-range^0.1.40.1.5up to date
 httpdate^1.0.11.0.3up to date
 hyper^1.0.01.5.0up to date
 mime_guess^2.0.12.0.5up to date
 percent-encoding^2.1.02.3.1up to date
 rand^0.8.40.8.5up to date
 tokio ⚠️^1.0.01.41.1maybe insecure
 url^2.1.02.5.3up to date
 winapi^0.3.60.3.9up to date

Dev dependencies

(5 total, 1 possibly insecure)

CrateRequiredLatestStatus
 http-body-util^0.1.00.1.2up to date
 hyper^1.0.01.5.0up to date
 hyper-util^0.1.10.1.10up to date
 tempfile^33.14.0up to date
 tokio ⚠️^1.0.01.41.1maybe 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);