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, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| base64 | ^0.22.0 | 0.22.1 | up to 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.35 | up to date |
| http | ^1 | 1.2.0 | up to 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.7 | 0.8.1 | out of date |
| rustls ⚠️ | ^0.23.0 | 0.23.20 | maybe insecure |
| serde | ^1.0.143 | 1.0.216 | up to date |
| serde_json | ^1.0.83 | 1.0.134 | up to date |
| serde_urlencoded | ^0.7.1 | 0.7.1 | up to date |
| url | ^2.2.2 | 2.5.4 | up to date |
| webpki-roots | ^0.26.0 | 0.26.7 | up to date |
(12 total, 3 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0.61 | 1.0.95 | up to date |
| env_logger | ^0.11.0 | 0.11.6 | up to date |
| futures-util | ^0.3.23 | 0.3.31 | up to date |
| http | ^0.2 | 1.2.0 | out of date |
| hyper | ^0.14.20 | 1.5.2 | 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 | ^2 | 2.2.0 | up to date |
| tokio ⚠️ | ^1.20.1 | 1.42.0 | maybe insecure |
| tokio-rustls | ^0.25.0 | 0.26.1 | out of date |
| tokio-stream | ^0.1.9 | 0.1.17 | 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 network-reachable panic in `Acceptor::accept`A bug introduced in rustls 0.23.13 leads to a panic if the received
TLS ClientHello is fragmented. Only servers that use
rustls::server::Acceptor::accept() are affected.
Servers that use tokio-rustls's LazyConfigAcceptor API are affected.
Servers that use tokio-rustls's TlsAcceptor API are not affected.
Servers that use rustls-ffi's rustls_acceptor_accept API are affected.