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.
facet-core(25 total, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bytes ⚠️ | ^1.11.0 | 1.11.1 | maybe insecure |
| bytestring | ^1.4.0 | 1.5.0 | up to date |
| camino | ^1.2.1 | 1.2.2 | up to date |
| chrono | ^0.4.42 | 0.4.44 | up to date |
| compact_str | ^0.9.0 | 0.9.0 | up to date |
| const-fnv1a-hash | ^1 | 1.1.0 | up to date |
| iddqd | ^0.3 | 0.3.17 | up to date |
| impls | ^1 | 1.0.3 | up to date |
| indexmap | ^2.12.1 | 2.13.0 | up to date |
| jiff | ^0.2.16 | 0.2.23 | up to date |
| lock_api | ^0.4 | 0.4.14 | up to date |
| num-complex | ^0.4.6 | 0.4.6 | up to date |
| ordered-float | ^5.0.0 | 5.3.0 | up to date |
| ruint ⚠️ | ^1.17.0 | 1.17.2 | maybe insecure |
| rust_decimal | ^1.38.0 | 1.41.0 | up to date |
| smallvec | ^1.15 | 1.15.1 | up to date |
| smartstring | ^1.0.1 | 1.0.1 | up to date |
| smol_str | ^0.3.4 | 0.3.6 | up to date |
| stable_deref_trait | ^1.2.1 | 1.2.1 | up to date |
| tendril | ^0.5.0 | 0.5.0 | up to date |
| time ⚠️ | ^0.3.44 | 0.3.47 | maybe insecure |
| ulid | ^1.2.1 | 1.2.1 | up to date |
| url | ^2.5.4 | 2.5.8 | up to date |
| uuid | ^1.19.0 | 1.23.0 | up to date |
| yoke | ^0.8.1 | 0.8.2 | up to date |
(1 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| parking_lot | ^0.12 | 0.12.5 | up to date |
ruint: Unsoundness of safe `reciprocal_mg10`The function reciprocal_mg10 is marked as safe but can trigger undefined behavior (out-of-bounds access) because it relies on debug_assert! for safety checks instead of assert!.
When compiled in release mode, the debug_assert! is optimized out, potentially allowing invalid inputs to cause memory corruption.
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.
time: Denial of Service via Stack ExhaustionWhen user-provided input is provided to any type that parses with the RFC 2822 format, a denial of service attack via stack exhaustion is possible. The attack relies on formally deprecated and rarely-used features that are part of the RFC 2822 format used in a malicious manner. Ordinary, non-malicious input will never encounter this scenario.
A limit to the depth of recursion was added in v0.3.47. From this version, an error will be returned rather than exhausting the stack.
Limiting the length of user input is the simplest way to avoid stack exhaustion, as the amount of the stack consumed would be at most a factor of the length of the input.