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.
actix-web-lab(33 total, 4 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-files | ^0.6 | 0.6.10 | up to date |
| actix-http | ^3.10 | 3.11.2 | up to date |
| actix-router | ^0.5 | 0.5.3 | up to date |
| actix-service | ^2 | 2.0.3 | up to date |
| actix-utils | ^3 | 3.0.1 | up to date |
| actix-web | ^4.9 | 4.12.1 | up to date |
| actix-web-lab-derive | ^0.24 | 0.24.0 | up to date |
| ahash | ^0.8 | 0.8.12 | up to date |
| arc-swap | ^1.1 | 1.8.1 | up to date |
| bytes ⚠️ | ^1 | 1.11.1 | maybe insecure |
| bytestring | ^1 | 1.5.0 | up to date |
| csv | ^1.1 | 1.4.0 | up to date |
| derive_more | ^2 | 2.1.1 | up to date |
| form_urlencoded | ^1 | 1.2.2 | up to date |
| futures-core | ^0.3.17 | 0.3.31 | up to date |
| futures-util | ^0.3.31 | 0.3.31 | up to date |
| http | ^0.2.7 | 1.4.0 | out of date |
| impl-more | ^0.1.9 | 0.3.1 | out of date |
| itertools | ^0.14 | 0.14.0 | up to date |
| local-channel | ^0.1 | 0.1.5 | up to date |
| mime | ^0.3 | 0.3.17 | up to date |
| pin-project-lite | ^0.2.16 | 0.2.16 | up to date |
| regex | ^1.11.0 | 1.12.3 | up to date |
| rmp-serde | ^1 | 1.3.1 | up to date |
| serde | ^1 | 1.0.228 | up to date |
| serde_cbor_2 | ^0.12.0-dev | 0.13.0 | out of date |
| serde_html_form | ^0.2 | 0.4.0 | out of date |
| serde_json | ^1 | 1.0.149 | up to date |
| serde_path_to_error | ^0.1 | 0.1.20 | up to date |
| tokio | ^1.38.2 | 1.49.0 | up to date |
| tokio-stream | ^0.1.17 | 0.1.18 | up to date |
| tracing | ^0.1.41 | 0.1.44 | up to date |
| url | ^2.1 | 2.5.8 | up to date |
(21 total, 4 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-web | ^4 | 4.12.1 | up to date |
| actix-web-lab-derive | ^0.24 | 0.24.0 | up to date |
| async_zip | ^0.0.17 | 0.0.18 | out of date |
| base64 | ^0.22 | 0.22.1 | up to date |
| digest | ^0.10 | 0.10.7 | up to date |
| ed25519-dalek | ^2 | 2.2.0 | up to date |
| env_logger | ^0.11 | 0.11.8 | up to date |
| futures-util | ^0.3.31 | 0.3.31 | up to date |
| generic-array | ^0.14 | 1.3.5 | out of date |
| hex | ^0.4 | 0.4.3 | up to date |
| hex-literal | ^0.4 | 1.1.0 | out of date |
| hmac | ^0.12 | 0.12.1 | up to date |
| rand | ^0.9 | 0.10.0 | out of date |
| rustls ⚠️ | ^0.23 | 0.23.36 | maybe insecure |
| rustls-pemfile | ^2 | 2.2.0 | up to date |
| serde | ^1 | 1.0.228 | up to date |
| sha2 | ^0.10 | 0.10.9 | up to date |
| static_assertions | ^1.1 | 1.1.0 | up to date |
| time | ^0.3 | 0.3.47 | up to date |
| tokio | ^1.38.2 | 1.49.0 | up to date |
| tokio-util | ^0.7 | 0.7.18 | 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.