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 s2n-quic-transport

Dependencies

(10 total, 2 possibly insecure)

CrateRequiredLatestStatus
 bytes^11.10.1up to date
 futures-channel^0.30.3.31up to date
 futures-core^0.30.3.31up to date
 hashbrown ⚠️^0.150.15.4maybe insecure
 intrusive-collections^0.90.9.7up to date
 once_cell^11.21.3up to date
 s2n-codec=0.61.00.61.0up to date
 s2n-quic-core=0.61.00.61.0up to date
 siphasher^1.01.0.1up to date
 smallvec ⚠️^11.15.1maybe insecure

Dev dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 bolero^0.130.13.4up to date
 futures-test^0.30.3.31up to date
 insta^11.43.1up 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.

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.