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-net

Dependencies

(25 total, 13 outdated, 4 possibly insecure)

CrateRequiredLatestStatus
 actix^0.7.60.13.5out of date
 bytes^0.41.10.1out of date
 futures^0.10.3.31out of date
 log^0.40.4.27up to date
 mio^0.6.131.0.4out of date
 native-tls^0.20.2.14up to date
 net2^0.20.2.39up to date
 num_cpus^1.01.17.0up to date
 openssl ⚠️^0.100.10.73maybe insecure
 rustls ⚠️^0.140.23.28out of date
 slab^0.40.4.10up to date
 tokio ⚠️^0.11.46.0out of date
 tokio-codec^0.10.1.2up to date
 tokio-current-thread^0.10.1.7up to date
 tokio-io^0.10.1.13up to date
 tokio-openssl^0.20.6.5out of date
 tokio-reactor^0.10.1.12up to date
 tokio-rustls^0.80.26.2out of date
 tokio-tcp^0.10.1.4up to date
 tokio-timer^0.20.2.13up to date
 tower-service^0.10.3.3out of date
 trust-dns-proto^0.5.00.23.2out of date
 trust-dns-resolver^0.10.00.23.2out of date
 webpki ⚠️^0.180.22.4out of date
 webpki-roots^0.151.0.1out of date

Dev dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 env_logger^0.50.11.8out of date

Security Vulnerabilities

tokio: Data race when sending and receiving after closing a `oneshot` channel

RUSTSEC-2021-0124

If a tokio::sync::oneshot channel is closed (via the oneshot::Receiver::close method), a data race may occur if the oneshot::Sender::send method is called while the corresponding oneshot::Receiver is awaited or calling try_recv.

When these methods are called concurrently on a closed channel, the two halves of the channel can concurrently access a shared memory location, resulting in a data race. This has been observed to cause memory corruption.

Note that the race only occurs when both halves of the channel are used after the Receiver half has called close. Code where close is not used, or where the Receiver is not awaited and try_recv is not called after calling close, is not affected.

See tokio#4225 for more details.

webpki: webpki: CPU denial of service in certificate path building

RUSTSEC-2023-0052

When this crate is given a pathological certificate chain to validate, it will spend CPU time exponential with the number of candidate certificates at each step of path building.

Both TLS clients and TLS servers that accept client certificate are affected.

This was previously reported in https://github.com/briansmith/webpki/issues/69 and re-reported recently by Luke Malinowski.

webpki 0.22.1 included a partial fix and webpki 0.22.2 added further fixes.

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.