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.
jsonrpsee-client-transport(17 total, 2 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| base64 | ^0.22 | 0.22.1 | up to date |
| futures-channel | ^0.3.14 | 0.3.31 | up to date |
| futures-util | ^0.3.14 | 0.3.31 | up to date |
| gloo-net | ^0.6.0 | 0.6.0 | up to date |
| http | ^1 | 1.2.0 | up to date |
| jsonrpsee-core | ^0.24.5 | 0.24.7 | up to date |
| pin-project | ^1 | 1.1.7 | up to date |
| rustls ⚠️ | ^0.23 | 0.23.20 | maybe insecure |
| rustls-pki-types | ^1 | 1.10.1 | up to date |
| rustls-platform-verifier | ^0.3.1 | 0.5.0 | out of date |
| soketto | ^0.8 | 0.8.1 | up to date |
| thiserror | ^1 | 2.0.9 | out of date |
| tokio | ^1.23.1 | 1.42.0 | up to date |
| tokio-rustls | ^0.26 | 0.26.1 | up to date |
| tokio-util | ^0.7 | 0.7.13 | up to date |
| tracing | ^0.1.34 | 0.1.41 | up to date |
| url | ^2.4.0 | 2.5.4 | 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.