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 axum-server

Dependencies

(17 total, 2 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 arc-swap^11.7.1up to date
 bytes^11.6.0up to date
 futures-util^0.30.3.30up to date
 http^1.0.01.1.0up to date
 http-body^1.0.01.0.0up to date
 http-body-util^0.1.00.1.1up to date
 hyper^1.0.11.3.1up to date
 hyper-util^0.1.10.1.3up to date
 openssl ⚠️^0.100.10.64maybe insecure
 pin-project-lite^0.20.2.14up to date
 rustls ⚠️^0.210.23.7out of date
 rustls-pemfile^2.0.02.1.2up to date
 tokio ⚠️^11.37.0maybe insecure
 tokio-openssl^0.60.6.4up to date
 tokio-rustls^0.240.26.0out of date
 tower^0.40.4.13up to date
 tower-service^0.30.3.2up to date

Dev dependencies

(6 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 axum^0.70.7.5up to date
 hyper^1.0.11.3.1up to date
 serial_test^2.03.1.1out of date
 tokio ⚠️^11.37.0maybe insecure
 tower^0.40.4.13up to date
 tower-http^0.5.00.5.2up 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);

openssl: `openssl` `X509VerifyParamRef::set_host` buffer over-read

RUSTSEC-2023-0044

When this function was passed an empty string, openssl would attempt to call strlen on it, reading arbitrary memory until it reached a NUL byte.

rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network input

RUSTSEC-2024-0336

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