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.
sprinkles-rs(43 total, 6 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| base64 | ^0.22 | 0.22.1 | up to date |
| blake3 | ^1.8 | 1.8.3 | up to date |
| bytes ⚠️ | ^1.10 | 1.11.1 | maybe insecure |
| cfg-if | ^1.0 | 1.0.4 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.44 | maybe insecure |
| clap | ^4.5 | 4.6.0 | up to date |
| const_format | ^0.2 | 0.2.35 | up to date |
| derive_more | ^2.0 | 2.1.1 | up to date |
| digest | ^0.10 | 0.11.2 | out of date |
| dirs | ^6.0 | 6.0.0 | up to date |
| dunce | ^1.0 | 1.0.5 | up to date |
| futures | ^0.3 | 0.3.32 | up to date |
| git2 | ^0.20 | 0.20.4 | up to date |
| gix | ^0.78 | 0.81.0 | out of date |
| gix-object | ^0.55 | 0.58.0 | out of date |
| indicatif | ^0.18 | 0.18.4 | up to date |
| itertools | ^0.14 | 0.14.0 | up to date |
| log | ^0.4 | 0.4.29 | up to date |
| md-5 | ^0.10 | 0.10.6 | up to date |
| phf | ^0.13 | 0.13.1 | up to date |
| quick-xml | ^0.39 | 0.39.2 | up to date |
| quork | ^0.9 | 0.9.1 | up to date |
| rayon | ^1.10 | 1.11.0 | up to date |
| regex | ^1.10 | 1.12.3 | up to date |
| reqwest | ^0.13 | 0.13.2 | up to date |
| semver | ^1.0 | 1.0.27 | up to date |
| serde | ^1.0 | 1.0.228 | up to date |
| serde_json | ^1.0 | 1.0.149 | up to date |
| serde_json_path | ^0.7 | 0.7.2 | up to date |
| serde_with | ^3.8 | 3.18.0 | up to date |
| sha1 | ^0.10 | 0.10.6 | up to date |
| sha2 | ^0.10 | 0.11.0 | out of date |
| strum | ^0.27 | 0.28.0 | out of date |
| sxd-document | ^0.3 | 0.3.2 | up to date |
| sxd-xpath | ^0.4 | 0.4.2 | up to date |
| thiserror | ^2.0 | 2.0.18 | up to date |
| tokio | ^1.44 | 1.50.0 | up to date |
| tokio-util | ^0.7 | 0.7.18 | up to date |
| url | ^2.5 | 2.5.8 | up to date |
| urlencoding | ^2.1 | 2.1.3 | up to date |
| which | ^8.0 | 8.0.2 | up to date |
| windows | ^0.62 | 0.62.2 | up to date |
| winreg | ^0.55 | 0.56.0 | out of date |
(6 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0 | 1.0.102 | up to date |
| async-std | ^1.13 | 1.13.2 | up to date |
| criterion | ^0.8 | 0.8.2 | up to date |
| rayon | ^1.10 | 1.11.0 | up to date |
| rstest | ^0.26 | 0.26.1 | up to date |
| tokio | ^1.37 | 1.50.0 | 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.