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.
http_req(9 total, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| base64 | ^0.22 | 0.22.1 | up to date |
| native-tls | ^0.2 | 0.2.14 | up to date |
| rustls ⚠️ | ^0.23 | 0.23.35 | maybe insecure |
| rustls-pemfile | ^2.2 | 2.2.0 | up to date |
| rustls-pki-types | ^1.13 | 1.13.1 | up to date |
| unicase | ^2.8 | 2.8.1 | up to date |
| webpki ⚠️ | ^0.22 | 0.22.4 | maybe insecure |
| webpki-roots | ^1.0 | 1.0.4 | up to date |
| zeroize | ^1.8 | 1.8.2 | 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 network-reachable panic in `Acceptor::accept`A bug introduced in rustls 0.23.13 leads to a panic if the received
TLS ClientHello is fragmented. Only servers that use
rustls::server::Acceptor::accept() are affected.
Servers that use tokio-rustls's LazyConfigAcceptor API are affected.
Servers that use tokio-rustls's TlsAcceptor API are not affected.
Servers that use rustls-ffi's rustls_acceptor_accept API are affected.