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.
async-compat(5 total, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| futures-core | ^0.3.5 | 0.3.31 | up to date |
| futures-io | ^0.3.5 | 0.3.31 | up to date |
| once_cell | ^1.4.1 | 1.20.2 | up to date |
| pin-project-lite | ^0.2 | 0.2.14 | up to date |
| tokio ⚠️ | ^1 | 1.40.0 | maybe insecure |
(5 total, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| blocking | ^1 | 1.6.1 | up to date |
| futures | ^0.3.5 | 0.3.31 | up to date |
| reqwest | ^0.12 | 0.12.8 | up to date |
| tokio ⚠️ | ^1 | 1.40.0 | maybe insecure |
| warp ⚠️ | ^0.3 | 0.3.7 | maybe insecure |
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);