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.
attohttpc(16 total, 5 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| base64 | ^0.21.2 | 0.22.1 | out of date |
| encoding_rs | ^0.8.31 | 0.8.35 | up to date |
| encoding_rs_io | ^0.1.7 | 0.1.7 | up to date |
| flate2 | ^1.0.24 | 1.0.34 | up to date |
| http | ^0.2.8 | 1.1.0 | out of date |
| log | ^0.4.17 | 0.4.22 | up to date |
| mime | ^0.3.16 | 0.3.17 | up to date |
| multipart | ^0.18.0 | 0.18.0 | up to date |
| native-tls | ^0.2.10 | 0.2.12 | up to date |
| rustls-native-certs | ^0.6 | 0.8.0 | out of date |
| rustls ⚠️ | ^0.21.0 | 0.23.16 | out of date |
| serde | ^1.0.143 | 1.0.214 | up to date |
| serde_json | ^1.0.83 | 1.0.132 | up to date |
| serde_urlencoded | ^0.7.1 | 0.7.1 | up to date |
| url | ^2.2.2 | 2.5.3 | up to date |
| webpki-roots | ^0.25.1 | 0.26.6 | out of date |
(12 total, 4 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0.61 | 1.0.93 | up to date |
| env_logger | ^0.10.0 | 0.11.5 | out of date |
| futures | ^0.3.23 | 0.3.31 | up to date |
| futures-util | ^0.3.23 | 0.3.31 | up to date |
| hyper | ^0.14.20 | 1.5.0 | out of date |
| lazy_static | ^1.4.0 | 1.5.0 | up to date |
| multipart | ^0.18.0 | 0.18.0 | up to date |
| rustls-pemfile | ^1.0.3 | 2.2.0 | out of date |
| tokio ⚠️ | ^1.20.1 | 1.41.1 | maybe insecure |
| tokio-rustls | ^0.24.1 | 0.26.0 | out of date |
| tokio-stream | ^0.1.9 | 0.1.16 | up to date |
| warp ⚠️ | ^0.3.2 | 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);
rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network inputIf a close_notify alert is received during a handshake, complete_io
does not terminate.
Callers which do not call complete_io are not affected.
rustls-tokio and rustls-ffi do not call complete_io
and are not affected.
rustls::Stream and rustls::StreamOwned types use
complete_io and are affected.