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

(17 total, 8 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.82up 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
 gloo-net^0.2.00.5.0out of date
 http^0.21.1.0out of date
 jsonrpsee-core^0.16.30.22.4out of date
 jsonrpsee-types^0.16.30.22.4out of date
 pin-project^11.1.5up to date
 rustls-native-certs^0.60.7.0out of date
 soketto^0.7.10.8.0out of date
 thiserror^11.0.59up to date
 tokio ⚠️^1.161.37.0maybe insecure
 tokio-rustls^0.24.10.26.0out of date
 tokio-util^0.70.7.10up to date
 tracing^0.1.340.1.40up to date
 webpki-roots^0.25.20.26.1out 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);