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

CrateRequiredLatestStatus
 alloy-chains^0.1.180.1.64up to date
 alloy-consensus^0.90.12.5out of date
 alloy-eips^0.90.12.5out of date
 alloy-json-rpc^0.90.12.5out of date
 alloy-network^0.90.12.5out of date
 alloy-network-primitives^0.90.12.5out of date
 alloy-node-bindings^0.90.12.5out of date
 alloy-primitives^0.8.150.8.23up to date
 alloy-pubsub^0.90.12.5out of date
 alloy-rpc-client^0.90.12.5out of date
 alloy-rpc-types^0.90.12.5out of date
 alloy-rpc-types-admin^0.90.12.5out of date
 alloy-rpc-types-anvil^0.90.12.5out of date
 alloy-rpc-types-debug^0.90.12.5out of date
 alloy-rpc-types-engine^0.90.12.5out of date
 alloy-rpc-types-eth^0.90.12.5out of date
 alloy-rpc-types-trace^0.90.12.5out of date
 alloy-rpc-types-txpool^0.90.12.5out of date
 alloy-signer^0.90.12.5out of date
 alloy-signer-local^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
 async-stream^0.30.3.6up to date
 async-trait^0.10.1.87up to date
 auto_impl^1.21.2.1up to date
 dashmap^6.06.1.0up to date
 futures^0.30.3.31up to date
 futures-utils-wasm^0.10.1.0up to date
 lru^0.120.13.0out of date
 parking_lot^0.12.30.12.3up to date
 pin-project^1.11.1.10up to date
 reqwest^0.120.12.14up to date
 schnellru^0.2.30.2.4up 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.44.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

(21 total, 9 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 alloy-consensus^0.90.12.5out of date
 alloy-node-bindings^0.90.12.5out of date
 alloy-primitives^0.8.150.8.23up to date
 alloy-rlp^0.3.90.3.11up to date
 alloy-rpc-client^0.90.12.5out of date
 alloy-rpc-types-engine^0.90.12.5out of date
 alloy-serde^0.90.12.5out of date
 alloy-signer^0.90.12.5out of date
 alloy-signer-local^0.90.12.5out of date
 alloy-sol-types^0.8.150.8.23up to date
 alloy-transport-http^0.90.12.5out of 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.130.14.0out of date
 reqwest^0.120.12.14up to date
 tempfile^3.103.19.0up to date
 tokio ⚠️^11.44.1maybe insecure
 tower^0.50.5.2up to date
 tower-http^0.6.10.6.2up 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);