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.
actix-connect 2.0.0
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.
actix-connect
(16 total, 11 outdated, 3 possibly insecure)
Crate | Required | Latest | Status |
---|---|---|---|
actix-codec | ^0.3.0 | 0.5.2 | out of date |
actix-rt | ^1.1.1 | 2.9.0 | out of date |
actix-service | ^1.0.6 | 2.0.2 | out of date |
actix-utils | ^2.0.0 | 3.0.1 | out of date |
derive_more | ^0.99.2 | 0.99.17 | up to date |
either | ^1.5.3 | 1.11.0 | up to date |
futures-util | ^0.3.4 | 0.3.30 | up to date |
http | ^0.2.0 | 1.1.0 | out of date |
log | ^0.4 | 0.4.21 | up to date |
openssl ⚠️ | ^0.10 | 0.10.64 | maybe insecure |
rustls ⚠️ | ^0.18.0 | 0.23.5 | out of date |
tokio-openssl | ^0.4.0 | 0.6.4 | out of date |
tokio-rustls | ^0.14.0 | 0.26.0 | out of date |
trust-dns-proto | ^0.19 | 0.23.2 | out of date |
trust-dns-resolver | ^0.19 | 0.23.2 | out of date |
webpki ⚠️ | ^0.21 | 0.22.4 | out of date |
openssl
: `openssl` `X509VerifyParamRef::set_host` buffer over-readWhen this function was passed an empty string, openssl
would attempt to call strlen
on it, reading arbitrary memory until it reached a NUL byte.
webpki
: webpki: CPU denial of service in certificate path buildingWhen 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 inputIf 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.