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.
minreq(13 total, 2 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| base64 | ^0.22 | 0.22.1 | up to date |
| log | ^0.4.0 | 0.4.32 | up to date |
| native-tls | ^0.2 | 0.2.18 | up to date |
| openssl ⚠️ | ^0.10.29 | 0.10.81 | maybe insecure |
| openssl-probe | ^0.1 | 0.2.1 | out of date |
| punycode | ^0.4.1 | 0.4.1 | up to date |
| rustls | ^0.23.35 | 0.23.40 | up to date |
| rustls-platform-verifier | ^0.6.2 | 0.7.0 | out of date |
| rustls-webpki ⚠️ | ^0.103.8 | 0.103.13 | maybe insecure |
| serde | ^1.0.101 | 1.0.228 | up to date |
| serde_json | ^1.0.0 | 1.0.150 | up to date |
| urlencoding | ^2.1.0 | 2.1.3 | up to date |
| webpki-roots | ^1.0.4 | 1.0.7 | up to date |
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.
rustls-webpki: Reachable panic in certificate revocation list parsingA panic was reachable when parsing certificate revocation lists via [BorrowedCertRevocationList::from_der]
or [OwnedCertRevocationList::from_der]. This was the result of mishandling a syntactically valid empty
BIT STRING appearing in the onlySomeReasons element of a IssuingDistributionPoint CRL extension.
This panic is reachable prior to a CRL's signature being verified.
Applications that do not use CRLs are not affected.
Thank you to @tynus3 for the report.