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 web3


(34 total, 9 outdated, 1 possibly insecure)

 arrayvec^ to date
 web3-async-native-tls^ to date
 async-std^ to date
 base64^ of date
 bytes^ to date
 derive_more^ to date
 ethabi^ of date
 ethereum-types^ of date
 futures^ to date
 futures-timer^ to date
 getrandom^ to date
 headers^ of date
 hex^ to date
 idna^ of date
 js-sys^0.3.450.3.69up to date
 jsonrpc-core^ to date
 log^ to date
 once_cell^ to date
 parking_lot^ to date
 pin-project^ to date
 rand^ to date
 reqwest^ of date
 rlp^ to date
 secp256k1^ of date
 serde^1.0.901.0.203up to date
 serde_json^1.0.391.0.117up to date
 soketto^ of date
 tiny-keccak^ to date
 tokio ⚠️^ insecure
 tokio-stream^ to date
 tokio-util^ of date
 url^ to date
 wasm-bindgen^0.2.680.2.92up to date
 wasm-bindgen-futures^ to date

Dev dependencies

(6 total, 3 outdated, 2 possibly insecure)

 env_logger^ of date
 hex-literal^ of date
 hyper ⚠️^ of date
 tokio ⚠️^ insecure
 tokio-stream^ to date
 wasm-bindgen-test^ to date

Security Vulnerabilities

hyper: Lenient `hyper` header parsing of `Content-Length` could allow request smuggling


hyper's HTTP header parser accepted, according to RFC 7230, illegal contents inside Content-Length headers. Due to this, upstream HTTP proxies that ignore the header may still forward them along if it chooses to ignore the error.

To be vulnerable, hyper must be used as an HTTP/1 server and using an HTTP proxy upstream that ignores the header's contents but still forwards it. Due to all the factors that must line up, an attack exploiting this vulnerability is unlikely.

hyper: Integer overflow in `hyper`'s parsing of the `Transfer-Encoding` header leads to data loss


When decoding chunk sizes that are too large, hyper's code would encounter an integer overflow. Depending on the situation, this could lead to data loss from an incorrect total size, or in rarer cases, a request smuggling attack.

To be vulnerable, you must be using hyper for any HTTP/1 purpose, including as a client or server, and consumers must send requests or responses that specify a chunk size greater than 18 exabytes. For a possible request smuggling attack to be possible, any upstream proxies must accept a chunk size greater than 64 bits.

tokio: reject_remote_clients Configuration corruption


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.


Ensure that pipe_mode is set first after initializing a ServerOptions. For example:

let mut opts = ServerOptions::new();