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 libp2p-gossipsub

Dependencies

(16 total, 9 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 base64^0.11.00.22.1out of date
 byteorder^1.3.21.5.0up to date
 bytes^0.5.41.6.0out of date
 fnv^1.0.61.0.7up to date
 futures^0.3.10.3.30up to date
 futures_codec^0.4.00.4.1up to date
 libp2p-core^0.20.00.41.2out of date
 libp2p-swarm^0.20.00.44.2out of date
 log^0.4.80.4.21up to date
 lru ⚠️^0.4.30.12.3out of date
 prost^0.6.10.12.6out of date
 rand^0.7.30.8.5out of date
 sha2^0.8.10.10.8out of date
 smallvec ⚠️^1.1.01.13.2maybe insecure
 unsigned-varint^0.4.00.8.0out of date
 wasm-timer^0.2.40.2.5up to date

Dev dependencies

(3 total, 2 outdated)

CrateRequiredLatestStatus
 async-std^1.6.21.12.0up to date
 env_logger^0.7.10.11.3out of date
 quickcheck^0.9.21.0.3out of 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.