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.
rust-embed(13 total, 7 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-web | ^3 | 4.5.1 | out of date |
| axum | ^0.4 | 0.7.5 | out of date |
| hex | ^0.4.3 | 0.4.3 | up to date |
| include-flate | ^0.1 | 0.3.0 | out of date |
| mime_guess | ^2 | 2.0.4 | up to date |
| poem | ^1.3.18 | 3.0.0 | out of date |
| rocket | ^0.5.0-rc.1 | 0.5.0 | up to date |
| rust-embed-impl | ^6.2.0 | 8.3.0 | out of date |
| rust-embed-utils | ^7.2.0 | 8.3.0 | out of date |
| salvo | ^0.16 | 0.67.0 | out of date |
| tokio ⚠️ | ^1.0 | 1.37.0 | maybe insecure |
| walkdir | ^2.3.1 | 2.5.0 | up to date |
| warp ⚠️ | ^0.3 | 0.3.7 | maybe insecure |
(1 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| sha2 | ^0.9 | 0.10.8 | out of date |
warp: Improper validation of Windows paths could lead to directory traversal attackPath 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 corruptionOn 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.
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);