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-ws-client

Dependencies

(16 total, 6 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 arrayvec^0.7.10.7.4up to date
 async-trait^0.10.1.79up to date
 fnv^11.0.7up to date
 futures^0.3.140.3.30up to date
 http^0.21.1.0out of date
 jsonrpsee-types^0.4.10.22.3out of date
 log^0.40.4.21up to date
 pin-project^11.1.5up to date
 rustls-native-certs^0.5.00.7.0out of date
 serde^11.0.197up to date
 serde_json^11.0.115up to date
 soketto^0.70.8.0out of date
 thiserror^11.0.58up to date
 tokio ⚠️^11.37.0maybe insecure
 tokio-rustls^0.220.26.0out of date
 tokio-util^0.60.7.10out of date

Dev dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 env_logger^0.90.11.3out of 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);