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 alloy-rpc-client

Dependencies

(18 total, 6 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 alloy-json-rpc^0.90.12.5out of date
 alloy-primitives^0.8.150.8.23up to date
 alloy-pubsub^0.90.12.5out of date
 alloy-transport^0.90.12.5out of date
 alloy-transport-http^0.90.12.5out of date
 alloy-transport-ipc^0.90.12.5out of date
 alloy-transport-ws^0.90.12.5out of date
 futures^0.30.3.31up to date
 pin-project^1.11.1.10up to date
 reqwest^0.120.12.14up to date
 serde^1.01.0.219up to date
 serde_json^1.01.0.140up to date
 tokio ⚠️^11.44.1maybe insecure
 tokio-stream^0.10.1.17up to date
 tower^0.50.5.2up to date
 tracing^0.10.1.41up to date
 url^2.52.5.4up to date
 wasmtimer^0.4.00.4.1up to date

Dev dependencies

(8 total, 3 outdated)

CrateRequiredLatestStatus
 alloy-node-bindings^0.90.12.5out of date
 alloy-primitives^0.8.150.8.23up to date
 alloy-transport-ipc^0.90.12.5out of date
 alloy-transport-ws^0.90.12.5out of date
 ci_info^0.14.140.14.14up to date
 futures-util^0.30.3.31up to date
 similar-asserts^1.51.7.0up to date
 tempfile^33.19.0up 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);