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, 7 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.10.1.88up to date
 fnv^11.0.7up to date
 futures^0.3.140.3.31up to date
 jsonrpsee-types^0.2.00.25.1out of date
 log^0.40.4.27up to date
 pin-project^11.1.10up to date
 rustls ⚠️^0.19.10.23.28out of date
 rustls-native-certs^0.5.00.8.1out of date
 serde^11.0.219up to date
 serde_json^11.0.140up to date
 soketto^0.50.8.1out of date
 thiserror^12.0.12out of date
 tokio ⚠️^11.46.0maybe insecure
 tokio-rustls^0.220.26.2out of date
 tokio-util^0.60.7.15out of date
 url^22.5.4up to date

Dev dependencies

(1 total, 1 outdated)

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

rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network input

RUSTSEC-2024-0336

If a close_notify alert is received during a handshake, complete_io does not terminate.

Callers which do not call complete_io are not affected.

rustls-tokio and rustls-ffi do not call complete_io and are not affected.

rustls::Stream and rustls::StreamOwned types use complete_io and are affected.