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

(18 total, 8 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.500.1.83up to date
 auto_impl^0.5.01.2.0out of date
 ethers-contract^1.0.02.0.14out of date
 ethers-core^1.0.02.0.14out of date
 ethers-etherscan^1.0.02.0.14out of date
 ethers-providers^1.0.02.0.14out of date
 ethers-signers^1.0.02.0.14out of date
 futures-locks^0.70.7.1up to date
 futures-util^0.30.3.31up to date
 instant^0.1.120.1.13up to date
 reqwest^0.11.130.12.9out of date
 serde^1.0.1241.0.214up to date
 serde_json^1.0.641.0.132up to date
 thiserror^1.02.0.0out of date
 tokio ⚠️^1.181.41.1maybe insecure
 tracing^0.1.370.1.40up to date
 tracing-futures^0.2.50.2.5up to date
 url^2.3.12.5.3up to date

Dev dependencies

(7 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 ethers-providers^1.0.02.0.14out of date
 ethers-solc^1.0.02.0.14out of date
 hex^0.4.30.4.3up to date
 once_cell^1.16.01.20.2up to date
 rand^0.8.50.8.5up to date
 serial_test^0.9.03.1.1out of date
 tokio ⚠️^1.181.41.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);