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.
first_aid_bot_core(6 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| csv | ^1.3 | 1.4.0 | up to date |
| bytes ⚠️ | ^1.6 | 1.11.1 | maybe insecure |
| reqwest | ^0.12 | 0.13.2 | out of date |
| indexmap | ^2.2 | 2.13.0 | up to date |
| const_format | ^0.2 | 0.2.35 | up to date |
| regex | ^1.10.4 | 1.12.3 | up to date |
(2 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| env_logger | ^0.11 | 0.11.9 | up to date |
| test-log | ^0.2 | 0.2.19 | up to date |
bot(6 total, 4 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| pretty_env_logger | ^0.5 | 0.5.0 | up to date |
| teloxide | ^0.12 | 0.17.0 | out of date |
| redis | ^0.25 | 1.0.3 | out of date |
| rand | ^0.8 | 0.10.0 | out of date |
| itertools | ^0.12 | 0.14.0 | out of date |
| futures | ^0.3 | 0.3.31 | up to date |
rust_lib_app(2 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| openssl ⚠️ | ^0.10 | 0.10.75 | maybe insecure |
| flutter_rust_bridge | =2.0.0-dev.32 | 2.11.1 | out of date |
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.