This project contains known security vulnerabilities. Find detailed information at the bottom.
hyper-rustls(8 total, 6 outdated, 1 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| http | ^0.2 | 1.5.0 | out of date |
| hyper | ^0.14 | 1.11.1 | out of date |
| log | ^0.4.4 | 0.4.34 | up to date |
| rustls ⚠️ | ^0.20.1 | 0.23.45 | insecure |
| rustls-native-certs | ^0.6 | 0.8.4 | out of date |
| tokio | ^1.0 | 1.53.1 | up to date |
| tokio-rustls | ^0.23 | 0.26.5 | out of date |
| webpki-roots | ^0.22 | 1.0.9 | out of date |
(5 total, 3 outdated, 1 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| futures-util | ^0.3.1 | 0.3.34 | up to date |
| hyper | ^0.14 | 1.11.1 | out of date |
| rustls ⚠️ | ^0.20.1 | 0.23.45 | insecure |
| rustls-pemfile | ^1.0.0 | 2.2.0 | out of date |
| tokio | ^1.0 | 1.53.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.