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.
polars-arrow(31 total, 5 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| polars-arrow-format | ^0.2.0 | 0.2.1 | up to date |
| async-stream | ^0.3 | 0.3.6 | up to date |
| atoi_simd | ^0.17 | 0.18.1 | out of date |
| avro-schema | ^0.3 | 0.3.0 | up to date |
| bitflags | ^2 | 2.11.0 | up to date |
| bytemuck | ^1.22 | 1.25.0 | up to date |
| bytes ⚠️ | ^1.11 | 1.11.1 | maybe insecure |
| chrono ⚠️ | <=0.4.41 | 0.4.44 | out of date |
| chrono-tz | ^0.10 | 0.10.4 | up to date |
| dyn-clone | ^1 | 1.0.20 | up to date |
| either | ^1.14 | 1.15.0 | up to date |
| ethnum | ^1.3.2 | 1.5.2 | up to date |
| futures | ^0.3.25 | 0.3.32 | up to date |
| getrandom | ^0.2 | 0.4.2 | out of date |
| half | ^2.7.1 | 2.7.1 | up to date |
| hashbrown | ^0.16.0 | 0.16.1 | up to date |
| itoa | ^1.0.6 | 1.0.18 | up to date |
| lz4 | ^1.24 | 1.28.1 | up to date |
| num-traits | ^0.2 | 0.2.19 | up to date |
| polars-buffer | ^0.53.0 | 0.53.0 | up to date |
| polars-error | ^0.53.0 | 0.53.0 | up to date |
| polars-schema | ^0.53.0 | 0.53.0 | up to date |
| polars-utils | ^0.53.0 | 0.53.0 | up to date |
| proptest | ^1.6 | 1.11.0 | up to date |
| schemars | ^0.9.0 | 1.2.1 | out of date |
| serde | ^1.0.188 | 1.0.228 | up to date |
| simdutf8 | ^0.1.4 | 0.1.5 | up to date |
| streaming-iterator | ^0.1.9 | 0.1.9 | up to date |
| strum_macros | ^0.27 | 0.28.0 | out of date |
| tokio | ^1.44 | 1.50.0 | up to date |
| zstd | ^0.13 | 0.13.3 | up to date |
(3 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| proptest | ^1.6 | 1.11.0 | up to date |
| rand | ^0.9 | 0.10.0 | out of date |
| tokio | ^1.44 | 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.