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 actix-tls

Dependencies

(19 total, 3 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 actix-rt^2.22.10.0up to date
 actix-service^22.0.3up to date
 actix-utils^33.0.1up to date
 futures-core^0.3.70.3.31up to date
 http^11.3.1up to date
 impl-more^0.10.1.9up to date
 pin-project-lite^0.2.70.2.16up to date
 rustls ⚠️^0.21.60.23.26out of date
 rustls-native-certs^0.70.8.1out of date
 rustls-pki-types^11.11.0up to date
 rustls-webpki^0.101.40.103.1out of date
 openssl ⚠️^0.10.550.10.72maybe insecure
 tokio^1.23.11.44.2up to date
 tokio-native-tls^0.30.3.1up to date
 tokio-openssl^0.60.6.5up to date
 tokio-rustls^0.260.26.2up to date
 tokio-util^0.70.7.14up to date
 tracing^0.1.300.1.41up to date
 webpki-roots^0.260.26.8up to date

Dev dependencies

(11 total, 2 outdated)

CrateRequiredLatestStatus
 actix-codec^0.50.5.2up to date
 actix-rt^2.22.10.0up to date
 actix-server^22.5.1up to date
 bytes^11.10.1up to date
 futures-util^0.3.170.3.31up to date
 itertools^0.120.14.0out of date
 pretty_env_logger^0.50.5.0up to date
 rcgen^0.120.13.2out of date
 rustls-pemfile^22.2.0up to date
 tokio-rustls^0.260.26.2up to date
 trust-dns-resolver^0.230.23.2up to date

Security Vulnerabilities

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.

openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`

RUSTSEC-2025-0022

When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.

In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).

The maintainers thank quitbug for reporting this vulnerability to us.