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.

Crate tokio-rustls-acme

Dependencies

(21 total, 1 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.530.1.87up to date
 axum-server^0.70.7.1up to date
 base64^0.220.22.1up to date
 chrono^0.4.240.4.40up to date
 futures^0.3.210.3.31up to date
 log^0.4.170.4.26up to date
 num-bigint^0.4.40.4.6up to date
 pem^3.03.0.5up to date
 proc-macro2^1.0.781.0.94up to date
 rcgen^0.130.13.2up to date
 reqwest^0.120.12.14up to date
 ring ⚠️^0.17.00.17.14maybe insecure
 rustls ⚠️^0.230.23.23maybe insecure
 serde^1.0.1371.0.219up to date
 serde_json^1.0.811.0.140up to date
 thiserror^2.02.0.12up to date
 time^0.3.360.3.39up to date
 tokio ⚠️^1.20.11.44.1maybe insecure
 tokio-rustls^0.260.26.2up to date
 webpki-roots^0.260.26.8up to date
 x509-parser^0.160.17.0out of date

Dev dependencies

(8 total, 1 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 axum^0.70.8.1out of date
 clap^44.5.32up to date
 simple_logger^5.05.0.0up to date
 structopt^0.3.260.3.26up to date
 tokio ⚠️^1.19.21.44.1maybe insecure
 tokio-stream^0.1.90.1.17up to date
 tokio-util^0.7.30.7.14up to date
 warp ⚠️^0.30.3.7maybe insecure

Security Vulnerabilities

warp: Improper validation of Windows paths could lead to directory traversal attack

RUSTSEC-2022-0082

Path 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 corruption

RUSTSEC-2023-0001

On 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.

Workarounds

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`

RUSTSEC-2024-0399

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.

RUSTSEC-2025-0009

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.