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.
awc(28 total, 5 outdated, 4 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-codec | ^0.5 | 0.5.3 | up to date |
| actix-http | ^3.7 | 3.13.5 | up to date |
| actix-rt | ^2.1 | 2.13.0 | up to date |
| actix-service | ^2 | 2.0.3 | up to date |
| actix-tls | ^3.4 | 3.5.0 | up to date |
| actix-utils | ^3 | 3.0.1 | up to date |
| base64 | ^0.22 | 0.23.1 | out of date |
| bytes ⚠️ | ^1 | 1.12.1 | maybe insecure |
| cfg-if | ^1 | 1.0.4 | up to date |
| cookie | ^0.16 | 0.18.2 | out of date |
| derive_more | ^2 | 2.1.1 | up to date |
| futures-core | ^0.3.17 | 0.3.34 | up to date |
| futures-util | ^0.3.17 | 0.3.34 | up to date |
| h2 ⚠️ | ^0.3.26 | 0.4.19 | out of date |
| http | ^0.2.7 | 1.5.0 | out of date |
| itoa | ^1 | 1.0.18 | up to date |
| log | ^0.4 | 0.4.34 | up to date |
| mime | ^0.3 | 0.3.17 | up to date |
| percent-encoding | ^2.1 | 2.3.2 | up to date |
| pin-project-lite | ^0.2 | 0.2.17 | up to date |
| rand | ^0.9 | 0.10.2 | out of date |
| serde | ^1.0 | 1.0.229 | up to date |
| serde_json | ^1.0 | 1.0.151 | up to date |
| serde_urlencoded | ^0.7 | 0.7.1 | up to date |
| openssl ⚠️ | ^0.10.55 | 0.10.81 | maybe insecure |
| rustls ⚠️ | ^0.23 | 0.23.44 | maybe insecure |
| tokio | ^1.24.2 | 1.53.1 | up to date |
| trust-dns-resolver | ^0.23 | 0.23.2 | up to date |
(18 total, 4 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-http | ^3.7 | 3.13.5 | up to date |
| actix-http-test | ^3 | 3.2.0 | up to date |
| actix-server | ^2 | 2.9.1 | up to date |
| actix-test | ^0.1 | 0.1.5 | up to date |
| actix-tls | ^3.4 | 3.5.0 | up to date |
| actix-utils | ^3 | 3.0.1 | up to date |
| actix-web | ^4 | 4.15.0 | up to date |
| brotli | ^7 | 9.0.0 | out of date |
| const-str | ^0.5 | 1.1.0 | out of date |
| env_logger | ^0.11 | 0.11.11 | up to date |
| flate2 | ^1.0.13 | 1.1.10 | up to date |
| futures-util | ^0.3.17 | 0.3.34 | up to date |
| rcgen | ^0.13 | 0.14.10 | out of date |
| rustls-pemfile | ^2 | 2.2.0 | up to date |
| static_assertions | ^1.1 | 1.1.0 | up to date |
| rustls ⚠️ | ^0.23 | 0.23.44 | maybe insecure |
| tokio | ^1.24.2 | 1.53.1 | up to date |
| zstd | ^0.13 | 0.14.0 | 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.
openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.
In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).
The maintainers thank quitbug for reporting this vulnerability to us.
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.
h2: h2 unbounded empty DATA framesThe h2 crate, used internally by hyper, had a flaw that would accept and queue empty DATA frames without limit. If streams were not actively drained, this could lead to unbounded memory usage, or a panic if the length overflows.
Low severity.
Patched in v0.4.16.