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.
wasmio(16 total, 7 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-stream | ^0.3 | 0.3.6 | up to date |
| axum-serde | ^0.2 | 0.9.0 | out of date |
| axum-extra | ^0.9 | 0.12.5 | out of date |
| base64ct | ^1 | 1.8.3 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.44 | maybe insecure |
| dotenv | ^0.15 | 0.15.0 | up to date |
| headers | ^0.4 | 0.4.1 | up to date |
| if_chain | ^1.0.2 | 1.0.3 | up to date |
| quick-xml | ^0.31 | 0.39.2 | out of date |
| serde_json | ^1 | 1.0.149 | up to date |
| parking_lot | =0.12.1 | 0.12.5 | out of date |
| sha2 | ^0.10 | 0.11.0 | out of date |
| strum | ^0.26 | 0.28.0 | out of date |
| thiserror | ^1 | 2.0.18 | out of date |
| ulid | ^1 | 1.2.1 | up to date |
| urlencoding | ^2 | 2.1.3 | up to date |
(8 total, 2 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bytes ⚠️ | ^1 | 1.11.1 | maybe insecure |
| tempfile | ^3 | 3.27.0 | up to date |
| insta | ^1 | 1.46.3 | up to date |
| http-body-util | ^0.1 | 0.1.3 | up to date |
| http | ^1 | 1.4.0 | up to date |
| rand | ^0.8 | 0.10.0 | out of date |
| wasm-bindgen-futures | =0.4.40 | 0.4.64 | out of date |
| ntest | ^0.9 | 0.9.5 | up to date |
(1 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| chrono | ^0.4.33 | 0.4.44 | up to date |
wasmio-aws-types(2 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| derivative | ^2 | 2.2.0 | up to date |
| derive_builder | ^0.13 | 0.20.2 | out of 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.