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.
ethers-core(22 total, 6 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| arrayvec | ^0.7 | 0.7.6 | up to date |
| bytes ⚠️ | ^1.4 | 1.11.1 | maybe insecure |
| cargo_metadata | ^0.18.0 | 0.23.1 | out of date |
| chrono ⚠️ | ^0.4 | 0.4.44 | maybe insecure |
| elliptic-curve | ^0.13.5 | 0.13.8 | up to date |
| ethabi | ^18.0.0 | 18.0.0 | up to date |
| generic-array | ^0.14.7 | 1.3.5 | out of date |
| const-hex | ^1.6 | 1.18.1 | up to date |
| k256 | ^0.13.1 | 0.13.4 | up to date |
| num_enum | ^0.7 | 0.7.6 | up to date |
| once_cell | ^1.18 | 1.21.4 | up to date |
| open-fastrlp | ^0.1.4 | 0.1.4 | up to date |
| rand | ^0.8 | 0.10.0 | out of date |
| rlp | ^0.5 | 0.6.1 | out of date |
| serde | ^1.0 | 1.0.228 | up to date |
| serde_json | ^1.0 | 1.0.149 | up to date |
| strum | ^0.26.1 | 0.28.0 | out of date |
| syn | ^2.0 | 2.0.117 | up to date |
| tempfile | ^3.8 | 3.27.0 | up to date |
| thiserror | ^1.0 | 2.0.18 | out of date |
| tiny-keccak | ^2.0.2 | 2.0.2 | up to date |
| unicode-xid | ^0.2 | 0.2.6 | up to date |
(4 total, 3 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bincode | ^1.3.3 | 3.0.0 | out of date |
| hex-literal | ^0.4 | 1.1.0 | out of date |
| once_cell | ^1.18 | 1.21.4 | up to date |
| rand | ^0.8 | 0.10.0 | out of date |
chrono: Potential segfault in `localtime_r` invocationsUnix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.
No workarounds are known.
bytes: Integer overflow in `BytesMut::reserve`In the unique reclaim path of BytesMut::reserve, the condition
if v_capacity >= new_cap + offset
uses an unchecked addition. When new_cap + offset overflows usize in release builds, this condition may incorrectly pass, causing self.cap to be set to a value that exceeds the actual allocated capacity. Subsequent APIs such as spare_capacity_mut() then trust this corrupted cap value and may create out-of-bounds slices, leading to UB.
This behavior is observable in release builds (integer overflow wraps), whereas debug builds panic due to overflow checks.
use bytes::*;
fn main() {
let mut a = BytesMut::from(&b"hello world"[..]);
let mut b = a.split_off(5);
// Ensure b becomes the unique owner of the backing storage
drop(a);
// Trigger overflow in new_cap + offset inside reserve
b.reserve(usize::MAX - 6);
// This call relies on the corrupted cap and may cause UB & HBO
b.put_u8(b'h');
}
Users of BytesMut::reserve are only affected if integer overflow checks are configured to wrap. When integer overflow is configured to panic, this issue does not apply.