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.
hyper-http-proxy(15 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bytes ⚠️ | ^1.5 | 1.12.1 | maybe insecure |
| futures-util | ^0.3 | 0.3.34 | up to date |
| headers | ^0.4 | 0.4.1 | up to date |
| http | ^1 | 1.5.0 | up to date |
| hyper | ^1 | 1.11.1 | up to date |
| hyper-rustls | ^0.27 | 0.27.9 | up to date |
| hyper-tls | ^0.6 | 0.6.0 | up to date |
| hyper-util | ^0.1 | 0.1.20 | up to date |
| native-tls | ^0.2 | 0.2.18 | up to date |
| pin-project-lite | ^0.2 | 0.2.17 | up to date |
| tokio | ^1.35 | 1.53.1 | up to date |
| tokio-native-tls | ^0.3 | 0.3.1 | up to date |
| tokio-rustls | ^0.26 | 0.26.5 | up to date |
| tower-service | ^0.3 | 0.3.3 | up to date |
| webpki-roots | ^0.26 | 1.0.9 | out of date |
(6 total, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| futures | ^0.3 | 0.3.34 | up to date |
| http-body-util | ^0.1 | 0.1.5 | up to date |
| hyper | ^1.0 | 1.11.1 | up to date |
| hyper-util | ^0.1 | 0.1.20 | up to date |
| rustls ⚠️ | ^0.23 | 0.23.44 | maybe insecure |
| tokio | ^1.35 | 1.53.1 | 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.