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 rust-embed

Dependencies

(13 total, 3 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 actix-web^44.8.0up to date
 axum^0.70.7.5up to date
 hex^0.4.30.4.3up to date
 include-flate^0.20.3.0out of date
 mime_guess^22.0.5up to date
 poem^1.3.303.0.3out of date
 rocket^0.5.0-rc.20.5.1up to date
 rust-embed-impl^8.4.08.5.0up to date
 rust-embed-utils^8.4.08.5.0up to date
 salvo^0.160.68.5out of date
 tokio ⚠️^1.01.39.1maybe insecure
 walkdir^2.3.22.5.0up to date
 warp ⚠️^0.30.3.7maybe insecure

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 sha2^0.100.10.8up to date

Security Vulnerabilities

warp: Improper validation of Windows paths could lead to directory traversal attack

RUSTSEC-2022-0082

Path resolution in warp::filters::fs::dir didn't correctly validate Windows paths meaning paths like /foo/bar/c:/windows/web/screen/img101.png would be allowed and respond with the contents of c:/windows/web/screen/img101.png. Thus users could potentially read files anywhere on the filesystem.

This only impacts Windows. Linux and other unix likes are not impacted by this.

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);