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

(22 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.82up to date
 arrayvec^0.7.10.7.4up to date
 async-lock^2.43.3.0out of date
 async-trait^0.10.1.80up to date
 beef^0.5.10.5.2up to date
 futures-channel^0.3.140.3.30up to date
 futures-timer^33.0.3up to date
 futures-util^0.3.140.3.30up to date
 globset^0.40.4.14up to date
 http^0.2.71.1.0out of date
 hyper^0.14.101.3.1out of date
 jsonrpsee-types^0.16.30.22.4out of date
 parking_lot^0.120.12.2up to date
 rand^0.80.8.5up to date
 rustc-hash^11.1.0up to date
 serde^1.01.0.198up to date
 serde_json^11.0.116up to date
 soketto^0.7.10.8.0out of date
 thiserror^11.0.59up to date
 tokio ⚠️^1.161.37.0maybe insecure
 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.116up to date
 tokio ⚠️^1.161.37.0maybe 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);