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.
prost-build(9 total, 6 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bytes ⚠️ | ^1 | 1.11.1 | maybe insecure |
| heck | ^0.3 | 0.5.0 | out of date |
| itertools | ^0.9 | 0.14.0 | out of date |
| log | ^0.4 | 0.4.29 | up to date |
| multimap | ^0.8 | 0.10.1 | out of date |
| petgraph | ^0.5 | 0.8.3 | out of date |
| prost | ^0.7.0 | 0.14.3 | out of date |
| prost-types ⚠️ | ^0.7.0 | 0.14.3 | out of date |
| tempfile | ^3 | 3.27.0 | up to date |
(1 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| env_logger | ^0.8 | 0.11.9 | out of date |
prost-types: Conversion from `prost_types::Timestamp` to `SystemTime` can cause an overflow and panicAffected versions of this crate contained a bug in which untrusted input could cause an overflow and panic when converting a Timestamp to SystemTime.
It is recommended to upgrade to prost-types v0.8 and switch the usage of From<Timestamp> for SystemTime to TryFrom<Timestamp> for SystemTime.
See #438 for more information.
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.