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(22 total, 8 outdated, 4 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.1 | up to date |
| libc | ^0.2 | 0.2.183 | up to date |
| lru ⚠️ | ^0.7 | 0.16.3 | out of date |
| mysql_common | ^0.28.0 | 0.37.0 | out of date |
| named_pipe | ~0.4 | 0.4.1 | up to date |
| native-tls | ^0.2.3 | 0.2.18 | up to date |
| once_cell | ^1.7.2 | 1.21.4 | up to date |
| pem | ^1.0.1 | 3.0.6 | out of date |
| percent-encoding | ^2.1.0 | 2.3.2 | up to date |
| rustls ⚠️ | ^0.20.0 | 0.23.37 | out of date |
| rustls-pemfile | ^1.0.0 | 2.2.0 | out of date |
| serde | ^1 | 1.0.228 | up to date |
| serde_json | ^1 | 1.0.149 | up to date |
| socket2 | ^0.4 | 0.6.3 | 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.22.1 | 1.0.6 | out of date |
(5 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| frunk | ^0.4 | 0.4.4 | up to date |
| lazy_static | ^1.4.0 | 1.5.0 | 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 | maybe insecure |
lru: Use after free in lru crateLru crate has use after free vulnerability.
Lru crate has two functions for getting an iterator. Both iterators give references to key and value. Calling specific functions, like pop(), will remove and free the value, and but it's still possible to access the reference of value which is already dropped causing use after free.
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::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.
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.
time: Denial of Service via Stack ExhaustionWhen user-provided input is provided to any type that parses with the RFC 2822 format, a denial of service attack via stack exhaustion is possible. The attack relies on formally deprecated and rarely-used features that are part of the RFC 2822 format used in a malicious manner. Ordinary, non-malicious input will never encounter this scenario.
A limit to the depth of recursion was added in v0.3.47. From this version, an error will be returned rather than exhausting the stack.
Limiting the length of user input is the simplest way to avoid stack exhaustion, as the amount of the stack consumed would be at most a factor of the length of the input.