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 alloy-primitives

Dependencies

(26 total, 1 possibly insecure)

CrateRequiredLatestStatus
 allocative^0.3.20.3.4up to date
 alloy-rlp^0.30.3.10up to date
 arbitrary^1.31.4.1up to date
 bytes^11.9.0up to date
 cfg-if^1.0.01.0.0up to date
 derive_arbitrary^1.31.4.1up to date
 derive_more^1.01.0.0up to date
 foldhash^0.10.1.3up to date
 getrandom^0.20.2.15up to date
 hashbrown ⚠️^0.150.15.2maybe insecure
 const-hex^1.141.14.0up to date
 hex-literal^0.40.4.1up to date
 indexmap^2.52.7.0up to date
 itoa^11.0.14up to date
 k256^0.130.13.4up to date
 keccak-asm^0.1.00.1.4up to date
 paste^1.01.0.15up to date
 postgres-types^0.2.60.2.8up to date
 proptest^11.6.0up to date
 proptest-derive^0.50.5.1up to date
 rand^0.80.8.5up to date
 ruint^1.12.31.12.4up to date
 rustc-hash^2.02.1.0up to date
 serde^1.01.0.216up to date
 sha3^0.10.80.10.8up to date
 tiny-keccak^2.02.0.2up to date

Dev dependencies

(4 total, all up-to-date)

CrateRequiredLatestStatus
 bcs^0.1.60.1.6up to date
 bincode^1.31.3.3up to date
 criterion^0.50.5.1up to date
 serde_json^1.01.0.133up to date

Security Vulnerabilities

hashbrown: Borsh serialization of HashMap is non-canonical

RUSTSEC-2024-0402

The borsh serialization of the HashMap did not follow the borsh specification. It potentially produced non-canonical encodings dependent on insertion order. It also did not perform canonicty checks on decoding.

This can result in consensus splits and cause equivalent objects to be considered distinct.

This was patched in 0.15.1.