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.
mysql(21 total, 5 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bufstream | ~0.1 | 0.1.4 | up to date |
| bytes ⚠️ | ^1.0.1 | 1.11.1 | maybe insecure |
| crossbeam | ^0.8.1 | 0.8.4 | up to date |
| flate2 | ^1.0 | 1.1.9 | up to date |
| io-enum | ^1.0.0 | 1.2.0 | up to date |
| libc | ^0.2 | 0.2.180 | up to date |
| lru | ^0.12 | 0.16.3 | out of date |
| mysql_common | ^0.32 | 0.36.2 | out of date |
| named_pipe | ~0.4 | 0.4.1 | up to date |
| native-tls | ^0.2.3 | 0.2.14 | up to date |
| pem | ^3 | 3.0.6 | up to date |
| percent-encoding | ^2.1.0 | 2.3.2 | up to date |
| rustls ⚠️ | ^0.23 | 0.23.36 | maybe insecure |
| rustls-pemfile | ^2.1 | 2.2.0 | up to date |
| serde | ^1 | 1.0.228 | up to date |
| serde_json | ^1 | 1.0.149 | up to date |
| socket2 | ^0.5.2 | 0.6.2 | out of date |
| twox-hash | ^1 | 2.1.2 | out of date |
| url | ^2.1 | 2.5.8 | up to date |
| webpki ⚠️ | ^0.22.0 | 0.22.4 | maybe insecure |
| webpki-roots | ^0.26 | 1.0.6 | out of date |
(4 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| frunk | ^0.4 | 0.4.4 | up to date |
| rand | ^0.8.2 | 0.10.0 | out of date |
| serde_derive | ^1 | 1.0.228 | up to date |
| time | ^0.3 | 0.3.47 | up to date |
webpki: webpki: CPU denial of service in certificate path buildingWhen this crate is given a pathological certificate chain to validate, it will spend CPU time exponential with the number of candidate certificates at each step of path building.
Both TLS clients and TLS servers that accept client certificate are affected.
This was previously reported in https://github.com/briansmith/webpki/issues/69 and re-reported recently by Luke Malinowski.
webpki 0.22.1 included a partial fix and webpki 0.22.2 added further fixes.
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.