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.

Crate jsonrpsee-http-client

Dependencies

(17 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.10.1.83up to date
 base64^0.220.22.1up to date
 http-body^11.0.1up to date
 hyper^1.31.5.2up to date
 hyper-rustls^0.27.10.27.5up to date
 hyper-util^0.1.10.1.10up to date
 jsonrpsee-core^0.24.50.24.7up to date
 jsonrpsee-types^0.24.50.24.7up to date
 rustls ⚠️^0.23.70.23.20maybe insecure
 rustls-platform-verifier^0.30.5.0out of date
 serde^1.01.0.216up to date
 serde_json^11.0.133up to date
 thiserror^12.0.8out of date
 tokio^1.23.11.42.0up to date
 tower^0.4.130.5.2out of date
 tracing^0.1.340.1.41up to date
 url^2.4.02.5.4up to date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 tokio^1.23.11.42.0up to date
 tracing-subscriber^0.3.30.3.19up to date

Security Vulnerabilities

rustls: rustls network-reachable panic in `Acceptor::accept`

RUSTSEC-2024-0399

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.