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.
rustls-native-certs(4 total, 2 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| openssl-probe | >=0.1.2, <0.2.0 | 0.1.5 | up to date |
| rustls ⚠️ | >=0.19.0, <0.20.0 | 0.23.16 | out of date |
| schannel | >=0.1.15, <0.2.0 | 0.1.26 | up to date |
| security-framework | >=2.0.0, <3.0.0 | 3.0.0 | out of date |
(4 total, 3 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| ring | >=0.16.5, <0.17.0 | 0.17.8 | out of date |
| untrusted | >=0.7.0, <0.8.0 | 0.9.0 | out of date |
| webpki ⚠️ | >=0.21.0, <0.22.0 | 0.22.4 | out of date |
| webpki-roots | >=0.0.0, <1.0.0 | 0.26.6 | up to date |
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.