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 revm

Dependencies

(15 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 arrayref^0.30.3.7up to date
 auto_impl^1.01.1.0up to date
 bytes^1.11.5.0up to date
 futures^0.3.240.3.29up to date
 hashbrown^0.130.14.3out of date
 hex^0.40.4.3up to date
 num_enum^0.50.7.1out of date
 parking_lot^0.120.12.1up to date
 primitive-types^0.120.12.2up to date
 revm_precompiles^1.1.22.0.1out of date
 rlp^0.50.5.2up to date
 serde^1.01.0.193up to date
 sha3^0.100.10.8up to date
 tokio ⚠️^1.211.34.0maybe insecure
 web3^0.180.19.0out of 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);