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(21 total, 7 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-codec | ^0.4.0 | 0.5.2 | out of date |
| actix-http | ^3.0.0-beta.11 | 3.12.0 | up to date |
| actix-rt | ^2.1 | 2.11.0 | up to date |
| actix-service | ^2.0.0 | 2.0.3 | up to date |
| base64 | ^0.13 | 0.22.1 | out of date |
| bytes ⚠️ | ^1 | 1.11.1 | maybe insecure |
| cfg-if | ^1 | 1.0.4 | up to date |
| cookie | ^0.15 | 0.18.1 | out of date |
| derive_more | ^0.99.5 | 2.1.1 | out of date |
| futures-core | ^0.3.7 | 0.3.32 | up to date |
| itoa | ^0.4 | 1.0.17 | out of date |
| log | ^0.4 | 0.4.29 | 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.8 | 0.10.0 | out of date |
| serde | ^1.0 | 1.0.228 | up to date |
| serde_json | ^1.0 | 1.0.149 | up to date |
| serde_urlencoded | ^0.7 | 0.7.1 | up to date |
| openssl ⚠️ | ^0.10.9 | 0.10.76 | maybe insecure |
| rustls ⚠️ | ^0.20.0 | 0.23.37 | out of date |
rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network inputIf a close_notify alert is received during a handshake, complete_io
does not terminate.
Callers which do not call complete_io are not affected.
rustls-tokio and rustls-ffi do not call complete_io
and are not affected.
rustls::Stream and rustls::StreamOwned types use
complete_io and 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.