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(17 total, 4 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bytes ⚠️ | ^1 | 1.11.1 | maybe insecure |
| futures-channel | ^0.3 | 0.3.32 | up to date |
| futures-core | ^0.3 | 0.3.32 | up to date |
| futures-util | ^0.3 | 0.3.32 | up to date |
| h2 ⚠️ | ^0.3.24 | 0.4.13 | out of date |
| http | ^0.2 | 1.4.0 | out of date |
| http-body | ^0.4 | 1.0.1 | out of date |
| httparse | ^1.8 | 1.10.1 | up to date |
| httpdate | ^1.0 | 1.0.3 | up to date |
| itoa | ^1 | 1.0.17 | up to date |
| libc | ^0.2 | 0.2.182 | up to date |
| pin-project-lite | ^0.2.4 | 0.2.16 | up to date |
| socket2 | >=0.4.7, <0.6.0 | 0.6.2 | out of date |
| tokio | ^1.27 | 1.49.0 | up to date |
| tower-service | ^0.3 | 0.3.3 | up to date |
| tracing | ^0.1 | 0.1.44 | up to date |
| want | ^0.3 | 0.3.1 | up to date |
(13 total, 3 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| futures-util | ^0.3 | 0.3.32 | up to date |
| matches | ^0.1 | 0.1.10 | up to date |
| num_cpus | ^1.0 | 1.17.0 | up to date |
| pnet_datalink | ^0.27.2 | 0.35.0 | out of date |
| pretty_env_logger | ^0.4 | 0.5.0 | out of date |
| serde | ^1.0 | 1.0.228 | up to date |
| serde_json | ^1.0 | 1.0.149 | up to date |
| spmc | ^0.3 | 0.3.0 | up to date |
| tokio | ^1.27 | 1.49.0 | up to date |
| tokio-test | ^0.4 | 0.4.5 | up to date |
| tokio-util | ^0.7 | 0.7.18 | up to date |
| tower | ^0.4 | 0.5.3 | out of date |
| url | ^2.2 | 2.5.8 | up to date |
h2: Degradation of service in h2 servers with CONTINUATION FloodAn attacker can send a flood of CONTINUATION frames, causing h2 to process them indefinitely.
This results in an increase in CPU usage.
Tokio task budget helps prevent this from a complete denial-of-service, as the server can still respond to legitimate requests, albeit with increased latency.
More details at "https://seanmonstar.com/blog/hyper-http2-continuation-flood/.
Patches available for 0.4.x and 0.3.x versions.
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.