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

Dependencies

(16 total, 7 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.500.1.88up to date
 ethers-contract^0.6.02.0.14out of date
 ethers-core^0.6.02.0.14out of date
 ethers-etherscan^0.2.02.0.14out of date
 ethers-providers^0.6.02.0.14out of date
 ethers-signers^0.6.02.0.14out of date
 futures-util^0.3.180.3.31up to date
 instant^0.1.120.1.13up 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
 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

Dev dependencies

(7 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 ethers-providers^0.6.02.0.14out of date
 ethers-solc^0.1.02.0.14out of date
 hex^0.4.30.4.3up to date
 once_cell^1.8.01.21.3up to date
 rand^0.8.40.9.1out of date
 serial_test^0.5.13.2.0out of 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);