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.
may(14 total, 3 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| cfg-if | ^1 | 1.0.4 | up to date |
| core_affinity | ^0.8 | 0.8.3 | up to date |
| crossbeam | ^0.8 | 0.8.4 | up to date |
| fastrand | ^2.0 | 2.3.0 | up to date |
| generator | ^0.8 | 0.8.8 | up to date |
| libc | ^0.2 | 0.2.183 | up to date |
| log | ^0.4 | 0.4.29 | up to date |
| may_queue ⚠️ | ^0.1 | 0.1.23 | maybe insecure |
| nix | ^0.30 | 0.31.2 | out of date |
| num_cpus | ^1 | 1.17.0 | up to date |
| parking_lot | ^0.12 | 0.12.5 | up to date |
| smallvec ⚠️ | ^1 | 1.15.1 | maybe insecure |
| socket2 | ^0.5 | 0.6.3 | out of date |
| windows-sys | ^0.59 | 0.61.2 | out of date |
(8 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bytes ⚠️ | ^1.0 | 1.11.1 | maybe insecure |
| docopt | ^1.0 | 1.1.1 | up to date |
| httparse | ^1.1 | 1.10.1 | up to date |
| native-tls | ^0.2 | 0.2.18 | up to date |
| serde | ^1.0 | 1.0.228 | up to date |
| serde_derive | ^1.0 | 1.0.228 | up to date |
| tempfile | ^3 | 3.27.0 | up to date |
| tungstenite | ^0.26 | 0.28.0 | out of date |
may_queue: may_queue's Queue lacks Send/Sync bound for its Send/Sync trait.Affected versions of may_queue implements Send/Sync for its Queue type without restricting it to Sendable types and Syncable types.
This allows non-Sync types such as Cell to be shared across threads leading to undefined behavior and memory corruption in concurrent programs.
smallvec: Buffer overflow in SmallVec::insert_manyA 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.
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.