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.
tokio-rustls-acme(21 total, 8 outdated, 4 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-trait | ^0.1.53 | 0.1.92 | up to date |
| axum-server | ^0.7 | 0.8.0 | out of date |
| base64 | ^0.22 | 0.23.1 | out of date |
| chrono | ^0.4.24 | 0.4.45 | up to date |
| futures | ^0.3.21 | 0.3.33 | up to date |
| log | ^0.4.17 | 0.4.33 | up to date |
| num-bigint | ^0.4.4 | 0.5.1 | out of date |
| pem | ^3.0 | 4.0.0 | out of date |
| proc-macro2 | ^1.0.78 | 1.0.107 | up to date |
| rcgen | ^0.13 | 0.14.9 | out of date |
| reqwest | ^0.12 | 0.13.4 | out of date |
| ring ⚠️ | ^0.17.0 | 0.17.14 | maybe insecure |
| rustls ⚠️ | ^0.23 | 0.23.43 | maybe insecure |
| serde | ^1.0.137 | 1.0.229 | up to date |
| serde_json | ^1.0.81 | 1.0.151 | up to date |
| thiserror | ^2.0 | 2.0.20 | up to date |
| time ⚠️ | ^0.3.36 | 0.3.55 | maybe insecure |
| tokio ⚠️ | ^1.20.1 | 1.53.1 | maybe insecure |
| tokio-rustls | ^0.26 | 0.26.4 | up to date |
| webpki-roots | ^0.26 | 1.0.9 | out of date |
| x509-parser | ^0.16 | 0.18.1 | out of date |
(8 total, 2 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| axum | ^0.7 | 0.8.9 | out of date |
| clap | ^4 | 4.6.6 | up to date |
| simple_logger | ^5.0 | 5.2.0 | up to date |
| structopt | ^0.3.26 | 0.3.26 | up to date |
| tokio ⚠️ | ^1.19.2 | 1.53.1 | maybe insecure |
| tokio-stream | ^0.1.9 | 0.1.19 | up to date |
| tokio-util | ^0.7.3 | 0.7.19 | up to date |
| warp ⚠️ | ^0.3 | 0.4.3 | 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);
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.
ring: Some AES functions may panic when overflow checking is enabled.ring::aead::quic::HeaderProtectionKey::new_mask() may panic when overflow
checking is enabled. In the QUIC protocol, an attacker can induce this panic by
sending a specially-crafted packet. Even unintentionally it is likely to occur
in 1 out of every 2**32 packets sent and/or received.
On 64-bit targets operations using ring::aead::{AES_128_GCM, AES_256_GCM} may
panic when overflow checking is enabled, when encrypting/decrypting approximately
68,719,476,700 bytes (about 64 gigabytes) of data in a single chunk. Protocols
like TLS and SSH are not affected by this because those protocols break large
amounts of data into small chunks. Similarly, most applications will not
attempt to encrypt/decrypt 64GB of data in one chunk.
Overflow checking is not enabled in release mode by default, but
RUSTFLAGS="-C overflow-checks" or overflow-checks = true in the Cargo.toml
profile can override this. Overflow checking is usually enabled by default in
debug mode.
time: Denial of Service via Stack ExhaustionWhen user-provided input is provided to any type that parses with the RFC 2822 format, a denial of service attack via stack exhaustion is possible. The attack relies on formally deprecated and rarely-used features that are part of the RFC 2822 format used in a malicious manner. Ordinary, non-malicious input will never encounter this scenario.
A limit to the depth of recursion was added in v0.3.47. From this version, an error will be returned rather than exhausting the stack.
Limiting the length of user input is the simplest way to avoid stack exhaustion, as the amount of the stack consumed would be at most a factor of the length of the input.