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-platform-verifier(15 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| android_logger | ^0.15 | 0.15.1 | up to date |
| base64 | ^0.22 | 0.23.1 | out of date |
| core-foundation | ^0.10 | 0.10.1 | up to date |
| core-foundation-sys | ^0.8 | 0.8.7 | up to date |
| jni | ^0.22.4 | 0.22.4 | up to date |
| log | ^0.4 | 0.4.33 | up to date |
| once_cell | ^1.9 | 1.21.4 | up to date |
| rustls | ^0.23.27 | 0.23.43 | up to date |
| rustls-native-certs | ^0.8 | 0.8.4 | up to date |
| rustls-platform-verifier-android | ^0.1.0 | 0.1.1 | up to date |
| security-framework | ^3.5.0 | 3.7.0 | up to date |
| security-framework-sys | ^2.15 | 2.17.0 | up to date |
| rustls-webpki ⚠️ | ^0.103 | 0.103.13 | maybe insecure |
| webpki-root-certs | ^1 | 1.0.9 | up to date |
| windows-sys | >=0.52.0, <0.62.0 | 0.61.2 | up to date |
(2 total, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| rustls ⚠️ | ^0.23 | 0.23.43 | maybe insecure |
| webpki-root-certs | ^1 | 1.0.9 | up to date |
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.
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.