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.
sonic-rs(13 total, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| ahash | ^0.8 | 0.8.12 | up to date |
| bumpalo | ^3.19 | 3.20.2 | up to date |
| bytes ⚠️ | ^1.10 | 1.11.1 | maybe insecure |
| cfg-if | ^1.0 | 1.0.4 | up to date |
| faststr | ^0.2 | 0.2.34 | up to date |
| itoa | ^1.0 | 1.0.17 | up to date |
| ref-cast | ^1.0 | 1.0.25 | up to date |
| serde | ^1.0 | 1.0.228 | up to date |
| simdutf8 | ^0.1 | 0.1.5 | up to date |
| sonic-number | ^0.1 | 0.1.1 | up to date |
| sonic-simd | ^0.1 | 0.1.3 | up to date |
| thiserror | ^2.0 | 2.0.18 | up to date |
| zmij | ^1.0 | 1.0.21 | up to date |
(7 total, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bytes ⚠️ | ^1.4 | 1.11.1 | maybe insecure |
| chrono ⚠️ | ^0.4 | 0.4.44 | maybe insecure |
| encoding_rs | ^0.8 | 0.8.35 | up to date |
| paste | ^1.0 | 1.0.15 | up to date |
| serde_bytes | ^0.11 | 0.11.19 | up to date |
| serde_derive | ^1.0 | 1.0.228 | up to date |
| serde_json | ^1.0 | 1.0.149 | up to date |
chrono: Potential segfault in `localtime_r` invocationsUnix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.
No workarounds are known.
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.