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 parity-util-mem

Dependencies

(15 total, 9 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 cfg-if^0.1.101.0.0out of date
 dlmalloc^0.1.30.2.6out of date
 ethereum-types^0.9.00.14.1out of date
 hashbrown^0.60.14.5out of date
 impl-trait-for-tuples^0.1.30.2.2out of date
 jemallocator^0.3.20.5.4out of date
 libmimalloc-sys^0.1.140.1.37up to date
 lru ⚠️^0.40.12.3out of date
 mimalloc^0.1.180.1.41up to date
 parity-util-mem-derive^0.10.1.0up to date
 parking_lot^0.10.00.12.2out of date
 primitive-types^0.70.12.2out of date
 smallvec ⚠️^1.0.01.13.2maybe insecure
 wee_alloc^0.4.50.4.5up to date
 winapi^0.3.80.3.9up to date

Security Vulnerabilities

smallvec: Buffer overflow in SmallVec::insert_many

RUSTSEC-2021-0003

A bug in the SmallVec::insert_many method caused it to allocate a buffer that was smaller than needed. It then wrote past the end of the buffer, causing a buffer overflow and memory corruption on the heap.

This bug was only triggered if the iterator passed to insert_many yielded more items than the lower bound returned from its size_hint method.

The flaw was corrected in smallvec 0.6.14 and 1.6.1, by ensuring that additional space is always reserved for each item inserted. The fix also simplified the implementation of insert_many to use less unsafe code, so it is easier to verify its correctness.

Thank you to Yechan Bae (@Qwaz) and the Rust group at Georgia Tech’s SSLab for finding and reporting this bug.

lru: Use after free in lru crate

RUSTSEC-2021-0130

Lru crate has use after free vulnerability.

Lru crate has two functions for getting an iterator. Both iterators give references to key and value. Calling specific functions, like pop(), will remove and free the value, and but it's still possible to access the reference of value which is already dropped causing use after free.