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

Dependencies

(23 total, 12 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 arrayvec^0.7.20.7.6up to date
 bytes^1.1.01.10.1up to date
 cargo_metadata^0.14.10.20.0out of date
 convert_case^0.4.00.8.0out of date
 ecdsa^0.12.30.16.9out of date
 elliptic-curve^0.11.50.13.8out of date
 ethabi^15.018.0.0out of date
 futures-util^0.30.3.31up to date
 generic-array^0.14.41.2.0out of date
 hex^0.4.30.4.3up to date
 k256^0.9.50.13.4out of date
 once_cell^1.8.01.21.3up to date
 proc-macro2^1.0.331.0.95up to date
 quote^1.0.91.0.40up to date
 rand^0.8.40.9.1out of date
 rlp^0.5.00.6.1out of date
 rlp-derive^0.1.00.2.0out of date
 serde^1.0.1241.0.219up to date
 serde_json^1.0.641.0.140up to date
 syn^1.0.822.0.104out of date
 thiserror^1.0.302.0.12out of date
 tiny-keccak^2.0.22.0.2up to date
 tokio ⚠️^1.51.45.1maybe insecure

Dev dependencies

(6 total, 3 outdated)

CrateRequiredLatestStatus
 bincode^1.3.32.0.1out of date
 futures-util^0.30.3.31up to date
 hex-literal^0.3.41.0.0out of date
 once_cell^1.8.01.21.3up to date
 rand^0.8.40.9.1out of date
 serde_json^1.0.641.0.140up 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);