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

Dependencies

(16 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 futures-channel^0.3.140.3.30up to date
 futures-util^0.3.140.3.30up to date
 gloo-net^0.5.00.6.0out of date
 http^0.21.1.0out of date
 jsonrpsee-core^0.22.50.24.0out of date
 pin-project^11.1.5up to date
 rustls-native-certs^0.70.7.1up to date
 rustls-pki-types^11.7.0up to date
 soketto^0.7.10.8.0out of date
 thiserror^11.0.63up to date
 tokio ⚠️^1.161.39.1maybe insecure
 tokio-rustls^0.250.26.0out of date
 tokio-util^0.70.7.11up to date
 tracing^0.1.340.1.40up to date
 url^2.4.02.5.2up to date
 webpki-roots^0.260.26.3up 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);