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.
hyper-proxy2(19 total, 4 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bytes | ^1.5 | 1.10.1 | up to date |
| futures-util | ^0.3.30 | 0.3.31 | up to date |
| headers | ^0.4 | 0.4.1 | up to date |
| http | ^1.0 | 1.3.1 | up to date |
| hyper | ^1.0 | 1.6.0 | up to date |
| hyper-rustls | ^0.26.0 | 0.27.7 | out of date |
| hyper-tls | ^0.6.0 | 0.6.0 | up to date |
| hyper-util | ^0.1.2 | 0.1.14 | up to date |
| native-tls | ^0.2.11 | 0.2.14 | up to date |
| openssl ⚠️ | ^0.10.62 | 0.10.73 | maybe insecure |
| pin-project-lite | ^0.2.13 | 0.2.16 | up to date |
| rustls-native-certs | ^0.7.0 | 0.8.1 | out of date |
| tokio | ^1.35 | 1.46.0 | up to date |
| tokio-native-tls | ^0.3.1 | 0.3.1 | up to date |
| tokio-openssl | ^0.6.4 | 0.6.5 | up to date |
| tokio-rustls | ^0.25.0 | 0.26.2 | out of date |
| tower-service | ^0.3.2 | 0.3.3 | up to date |
| webpki ⚠️ | ^0.22 | 0.22.4 | maybe insecure |
| webpki-roots | ^0.26.0 | 1.0.1 | out of date |
(5 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| futures | ^0.3.30 | 0.3.31 | up to date |
| http-body-util | ^0.1.0 | 0.1.3 | up to date |
| hyper | ^1.0 | 1.6.0 | up to date |
| hyper-util | ^0.1.2 | 0.1.14 | up to date |
| tokio | ^1.35 | 1.46.0 | 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.
openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.
In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).
The maintainers thank quitbug for reporting this vulnerability to us.