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.
futures-rustls(3 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| futures-io | ^0.3 | 0.3.30 | up to date |
| rustls-pki-types | ^1 | 1.7.0 | up to date |
| rustls ⚠️ | ^0.22 | 0.23.5 | out of date |
(6 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| futures-util | ^0.3.1 | 0.3.30 | up to date |
| lazy_static | ^1 | 1.4.0 | up to date |
| rustls-pemfile | ^2 | 2.1.2 | up to date |
| smol | ^1 | 2.0.0 | out of date |
| rustls-webpki | ^0.102 | 0.102.3 | up to date |
| webpki-roots | ^0.26 | 0.26.1 | up to date |
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.