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

(22 total, 3 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.530.1.85up to date
 axum-server^0.70.7.1up to date
 base64^0.21.00.22.1out of date
 chrono^0.4.240.4.39up to date
 futures^0.3.210.3.31up to date
 log^0.4.170.4.25up to date
 num-bigint^0.4.40.4.6up to date
 pem^3.03.0.4up to date
 proc-macro2^1.0.781.0.93up to date
 rcgen^0.120.13.2out of date
 reqwest^0.120.12.12up to date
 ring^0.17.00.17.8up to date
 rustls ⚠️^0.230.23.21maybe insecure
 serde^1.0.1371.0.217up to date
 serde_json^1.0.811.0.137up to date
 thiserror^1.0.312.0.11out of date
 time^0.3.360.3.37up to date
 tokio ⚠️^1.20.11.43.0maybe insecure
 tokio-rustls^0.260.26.1up to date
 url^2.2.22.5.4up to date
 webpki-roots^0.260.26.7up to date
 x509-parser^0.160.16.0up to date

Dev dependencies

(8 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 axum^0.70.8.1out of date
 clap^44.5.27up to date
 simple_logger^4.15.0.0out of date
 structopt^0.3.260.3.26up to date
 tokio ⚠️^1.19.21.43.0maybe insecure
 tokio-stream^0.1.90.1.17up to date
 tokio-util^0.7.30.7.13up to date
 warp^0.3.70.3.7up to date

Security Vulnerabilities

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.