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 tower-serve-static

Dependencies

(14 total, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^11.8.0up to date
 futures-util^0.30.3.31up to date
 http^11.1.0up to date
 http-body^11.0.1up to date
 http-body-util^0.10.1.2up to date
 pin-project^11.1.7up to date
 tower-service^0.30.3.3up to date
 mime^0.30.3.17up to date
 mime_guess^22.0.5up to date
 tokio ⚠️^11.41.1maybe insecure
 tokio-util^0.70.7.12up to date
 percent-encoding^2.1.02.3.1up to date
 include_dir^0.7.30.7.4up to date
 httpdate^11.0.3up to date

Dev dependencies

(3 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 axum^0.7.30.7.9up to date
 tokio ⚠️^11.41.1maybe insecure
 tower^0.4.100.5.1out of 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);