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.
tame-index(19 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bytes ⚠️ | ^1.11 | 1.11.1 | maybe insecure |
| camino | ^1.1 | 1.2.2 | up to date |
| crossbeam-channel | ^0.5 | 0.5.15 | up to date |
| home | ^0.5 | 0.5.12 | up to date |
| http | ^1.3 | 1.4.0 | up to date |
| memchr | ^2.5 | 2.8.0 | up to date |
| rayon | ^1.7 | 1.11.0 | up to date |
| rustc-stable-hash | ^0.1 | 0.1.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 |
| sha2 | ^0.10 | 0.10.9 | up to date |
| smol_str | ^0.3 | 0.3.5 | up to date |
| thiserror | ^2.0 | 2.0.18 | up to date |
| tokio | ^1.48 | 1.49.0 | up to date |
| toml-span | ^0.6 | 0.7.0 | out of date |
| twox-hash | ^2.1 | 2.1.2 | up to date |
| reqwest | ^0.13 | 0.13.2 | up to date |
| libc | ^0.2 | 0.2.182 | up to date |
(7 total, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| cargo_metadata | ^0.23 | 0.23.1 | up to date |
| rayon | ^1.7 | 1.11.0 | up to date |
| reqwest | ^0.13 | 0.13.2 | up to date |
| rustls ⚠️ | ^0.23 | 0.23.36 | maybe insecure |
| tempfile | ^3.15 | 3.25.0 | up to date |
| tiny-bench | ^0.4 | 0.4.0 | up to date |
| webpki-roots | ^1.0 | 1.0.6 | up to date |
rustls: rustls network-reachable panic in `Acceptor::accept`A bug introduced in rustls 0.23.13 leads to a panic if the received
TLS ClientHello is fragmented. Only servers that use
rustls::server::Acceptor::accept() are affected.
Servers that use tokio-rustls's LazyConfigAcceptor API are affected.
Servers that use tokio-rustls's TlsAcceptor API are not affected.
Servers that use rustls-ffi's rustls_acceptor_accept API are affected.
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.