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.
tungstenite(16 total, 4 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| byteorder | ^1.3.2 | 1.5.0 | up to date |
| bytes ⚠️ | ^1.0 | 1.11.1 | maybe insecure |
| data-encoding | ^2 | 2.10.0 | up to date |
| http | ^1.0 | 1.4.0 | up to date |
| httparse | ^1.3.4 | 1.10.1 | up to date |
| log | ^0.4.8 | 0.4.29 | up to date |
| native-tls | ^0.2.3 | 0.2.14 | up to date |
| rand | ^0.8.0 | 0.10.0 | out of date |
| rustls ⚠️ | ^0.23.0 | 0.23.36 | maybe insecure |
| rustls-native-certs | ^0.7.0 | 0.8.3 | out of date |
| rustls-pki-types | ^1.0 | 1.14.0 | up to date |
| sha1 | ^0.10 | 0.10.6 | up to date |
| thiserror | ^1.0.23 | 2.0.18 | out of date |
| url | ^2.1.0 | 2.5.8 | up to date |
| utf-8 | ^0.7.5 | 0.7.6 | up to date |
| webpki-roots | ^0.26 | 1.0.6 | out of date |
(5 total, 4 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| criterion | ^0.5.0 | 0.8.2 | out of date |
| env_logger | ^0.10.0 | 0.11.8 | out of date |
| input_buffer | ^0.5.0 | 0.5.0 | up to date |
| rand | ^0.8.4 | 0.10.0 | out of date |
| socket2 | ^0.5.5 | 0.6.2 | out of 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.