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.
web3(34 total, 13 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| arrayvec | ^0.7.1 | 0.7.6 | up to date |
| web3-async-native-tls | ^0.4 | 0.4.0 | up to date |
| async-std | ^1.6 | 1.13.1 | up to date |
| base64 | ^0.13 | 0.22.1 | out of date |
| bytes | ^1.0 | 1.10.1 | up to date |
| derive_more | ^0.99.1 | 2.0.1 | out of date |
| ethabi | ^16.0.0 | 18.0.0 | out of date |
| ethereum-types | ^0.12.1 | 0.15.1 | out of date |
| futures | ^0.3.5 | 0.3.31 | up to date |
| futures-timer | ^3.0.2 | 3.0.3 | up to date |
| getrandom | ^0.2 | 0.3.3 | out of date |
| headers | ^0.3 | 0.4.1 | out of date |
| hex | ^0.4 | 0.4.3 | up to date |
| idna ⚠️ | ^0.2 | 1.0.3 | out of date |
| js-sys | ^0.3.45 | 0.3.77 | up to date |
| jsonrpc-core | ^18.0.0 | 18.0.0 | up to date |
| log | ^0.4.6 | 0.4.27 | up to date |
| once_cell | ^1.8.0 | 1.21.3 | up to date |
| parking_lot | ^0.12.0 | 0.12.4 | up to date |
| pin-project | ^1.0 | 1.1.10 | up to date |
| rand | ^0.8.1 | 0.9.1 | out of date |
| reqwest | ^0.11 | 0.12.22 | out of date |
| rlp | ^0.5 | 0.6.1 | out of date |
| secp256k1 | ^0.21 | 0.31.1 | out of date |
| serde | ^1.0.90 | 1.0.219 | up to date |
| serde_json | ^1.0.39 | 1.0.140 | up to date |
| soketto | ^0.7.0 | 0.8.1 | out of date |
| tiny-keccak | ^2.0.1 | 2.0.2 | up to date |
| tokio ⚠️ | ^1.0 | 1.46.1 | maybe insecure |
| tokio-stream | ^0.1 | 0.1.17 | up to date |
| tokio-util | ^0.6 | 0.7.15 | out of date |
| url | ^2.1 | 2.5.4 | up to date |
| wasm-bindgen | ^0.2.68 | 0.2.100 | up to date |
| wasm-bindgen-futures | ^0.4.18 | 0.4.50 | up to date |
(6 total, 3 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| env_logger | ^0.9 | 0.11.8 | out of date |
| hex-literal | ^0.3 | 1.0.0 | out of date |
| hyper ⚠️ | ^0.14 | 1.6.0 | out of date |
| tokio ⚠️ | ^1.0 | 1.46.1 | maybe insecure |
| tokio-stream | ^0.1 | 0.1.17 | up to date |
| wasm-bindgen-test | ^0.3.19 | 0.3.50 | up to date |
hyper: Lenient `hyper` header parsing of `Content-Length` could allow request smugglinghyper'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 lossWhen 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 corruptionOn 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();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);
idna: `idna` accepts Punycode labels that do not produce any non-ASCII when decodedidna 0.5.0 and earlier accepts Punycode labels that do not produce any non-ASCII output, which means that either ASCII labels or the empty root label can be masked such that they appear unequal without IDNA processing or when processed with a different implementation and equal when processed with idna 0.5.0 or earlier.
Concretely, example.org and xn--example-.org become equal after processing by idna 0.5.0 or earlier. Also, example.org.xn-- and example.org. become equal after processing by idna 0.5.0 or earlier.
In applications using idna (but not in idna itself) this may be able to lead to privilege escalation when host name comparison is part of a privilege check and the behavior is combined with a client that resolves domains with such labels instead of treating them as errors that preclude DNS resolution / URL fetching and with the attacker managing to introduce a DNS entry (and TLS certificate) for an xn---masked name that turns into the name of the target when processed by idna 0.5.0 or earlier.
Upgrade to idna 1.0.3 or later, if depending on idna directly, or to url 2.5.4 or later, if depending on idna via url. (This issue was fixed in idna 1.0.0, but versions earlier than 1.0.3 are not recommended for other reasons.)
When upgrading, please take a moment to read about alternative Unicode back ends for idna.
If you are using Rust earlier than 1.81 in combination with SQLx 0.8.2 or earlier, please also read an issue about combining them with url 2.5.4 and idna 1.0.3.
This issue resulted from idna 0.5.0 and earlier implementing the UTS 46 specification literally on this point and the specification having this bug. The specification bug has been fixed in revision 33 of UTS 46.
Thanks to kageshiron for recognizing the security implications of this behavior.