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

(12 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.10.1.81up to date
 hyper^0.14.101.4.1out of date
 hyper-rustls^0.240.27.2out of date
 jsonrpsee-core^0.22.50.24.0out of date
 jsonrpsee-types^0.22.50.24.0out of date
 serde^1.01.0.204up to date
 serde_json^1.01.0.120up to date
 thiserror^1.01.0.63up to date
 tokio ⚠️^1.161.39.1maybe insecure
 tower^0.4.130.4.13up to date
 tracing^0.1.340.1.40up to date
 url^2.4.02.5.2up to date

Dev dependencies

(2 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^1.161.39.1maybe insecure
 tracing-subscriber^0.3.30.3.18up to date

Security Vulnerabilities

tokio: reject_remote_clients Configuration corruption

RUSTSEC-2023-0001

On Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.

This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.

The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.

Workarounds

Ensure that pipe_mode is set first after initializing a ServerOptions. For example:

let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);