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 ethers-providers

Dependencies

(26 total, 7 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.500.1.88up to date
 auto_impl^0.5.01.3.0out of date
 bytes^1.1.01.10.1up to date
 ethers-core^0.6.02.0.14out of date
 futures-channel^0.3.160.3.31up to date
 futures-core^0.3.160.3.31up to date
 futures-timer^3.0.23.0.3up to date
 futures-util^0.3.180.3.31up to date
 hex^0.4.30.4.3up to date
 parking_lot^0.110.12.4out of date
 pin-project^1.0.71.1.10up to date
 reqwest^0.11.70.12.20out of date
 serde^1.0.1241.0.219up to date
 serde_json^1.0.641.0.140up to date
 thiserror^1.0.302.0.12out of date
 tokio ⚠️^1.51.45.1maybe insecure
 tokio-tungstenite^0.15.00.27.0out of date
 tokio-util^0.6.90.7.15out of date
 tracing^0.1.290.1.41up to date
 tracing-futures^0.2.50.2.5up to date
 url^2.2.22.5.4up to date
 wasm-bindgen^0.20.2.100up to date
 wasm-bindgen-futures^0.40.4.50up to date
 wasm-timer^0.20.2.5up to date
 web-sys^0.30.3.77up to date
 ws_stream_wasm^0.70.7.5up to date

Dev dependencies

(2 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tempfile^3.2.03.20.0up to date
 tokio ⚠️^1.51.45.1maybe insecure

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);