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-provider

Dependencies

(42 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 alloy-chains^0.20.2.3up to date
 alloy-consensus^1.01.0.9up to date
 alloy-eips^1.01.0.9up to date
 alloy-json-rpc^1.01.0.9up to date
 alloy-network^1.01.0.9up to date
 alloy-network-primitives^1.01.0.9up to date
 alloy-node-bindings^1.01.0.9up to date
 alloy-primitives^1.0.01.1.2up to date
 alloy-pubsub^1.01.0.9up to date
 alloy-rpc-client^1.01.0.9up to date
 alloy-rpc-types^1.01.0.9up to date
 alloy-rpc-types-admin^1.01.0.9up to date
 alloy-rpc-types-anvil^1.01.0.9up to date
 alloy-rpc-types-debug^1.01.0.9up to date
 alloy-rpc-types-engine^1.01.0.9up to date
 alloy-rpc-types-eth^1.01.0.9up to date
 alloy-rpc-types-trace^1.01.0.9up to date
 alloy-rpc-types-txpool^1.01.0.9up to date
 alloy-signer^1.01.0.9up to date
 alloy-sol-types^1.0.01.1.2up to date
 alloy-transport^1.01.0.9up to date
 alloy-transport-http^1.01.0.9up to date
 alloy-transport-ipc^1.01.0.9up to date
 alloy-transport-ws^1.01.0.9up to date
 async-stream^0.30.3.6up to date
 async-trait^0.10.1.88up to date
 auto_impl^1.21.3.0up to date
 dashmap^6.06.1.0up to date
 either^1.151.15.0up to date
 futures^0.30.3.31up to date
 futures-utils-wasm^0.10.1.0up to date
 lru^0.130.14.0out of date
 parking_lot^0.12.30.12.4up to date
 pin-project^1.11.1.10up to date
 reqwest^0.120.12.19up to date
 serde^1.01.0.219up to date
 serde_json^1.01.0.140up to date
 thiserror^2.02.0.12up to date
 tokio ⚠️^11.45.1maybe insecure
 tracing^0.10.1.41up to date
 url^2.52.5.4up to date
 wasmtimer^0.4.00.4.1up to date

Dev dependencies

(22 total, 1 possibly insecure)

CrateRequiredLatestStatus
 alloy-consensus^1.01.0.9up to date
 alloy-node-bindings^1.01.0.9up to date
 alloy-primitives^1.0.01.1.2up to date
 alloy-rlp^0.3.90.3.12up to date
 alloy-rpc-client^1.01.0.9up to date
 alloy-rpc-types-engine^1.01.0.9up to date
 alloy-serde^1.01.0.9up to date
 alloy-signer^1.01.0.9up to date
 alloy-signer-local^1.01.0.9up to date
 alloy-transport-http^1.01.0.9up to date
 ci_info^0.14.140.14.14up to date
 http^1.1.01.3.1up to date
 http-body-util^0.10.1.3up to date
 itertools>=0.13, <=0.140.14.0up to date
 jsonrpsee^0.250.25.1up to date
 reqwest^0.120.12.19up to date
 similar-asserts^1.51.7.0up to date
 tempfile^3.203.20.0up to date
 tokio ⚠️^11.45.1maybe insecure
 tower^0.50.5.2up to date
 tower-http^0.6.10.6.6up to date
 tracing-subscriber^0.30.3.19up 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);