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-core

Dependencies

(18 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.86up to date
 async-trait^0.10.1.81up to date
 beef^0.5.10.5.2up to date
 futures-timer^33.0.3up to date
 futures-util^0.3.140.3.30up to date
 hyper^0.14.101.4.1out of date
 jsonrpsee-types^0.22.50.24.0out of date
 parking_lot^0.120.12.3up to date
 pin-project^11.1.5up to date
 rand^0.80.8.5up to date
 rustc-hash^12.0.0out of date
 serde^1.01.0.204up to date
 serde_json^11.0.120up to date
 thiserror^11.0.63up to date
 tokio ⚠️^1.161.39.1maybe insecure
 tokio-stream^0.10.1.15up to date
 tracing^0.1.340.1.40up to date
 wasm-bindgen-futures^0.4.190.4.42up to date

Dev dependencies

(2 total, 1 possibly insecure)

CrateRequiredLatestStatus
 serde_json^1.01.0.120up to date
 tokio ⚠️^1.161.39.1maybe insecure

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);