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.
pdfium-render(19 total, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bitflags | ^2 | 2.11.0 | up to date |
| bytemuck | ^1 | 1.25.0 | up to date |
| bytes ⚠️ | ^1 | 1.11.1 | maybe insecure |
| chrono ⚠️ | ^0 | 0.4.44 | maybe insecure |
| console_error_panic_hook | ^0 | 0.1.7 | up to date |
| console_log | ^1 | 1.0.0 | up to date |
| image | ^0.25 | 0.25.10 | up to date |
| itertools | ^0 | 0.14.0 | up to date |
| js-sys | ^0 | 0.3.92 | up to date |
| libloading | ^0 | 0.9.0 | up to date |
| log | ^0 | 0.4.29 | up to date |
| maybe-owned | ^0 | 0.3.4 | up to date |
| once_cell | ^1 | 1.21.4 | up to date |
| utf16string | ^0 | 0.2.0 | up to date |
| vecmath | ^1 | 1.0.0 | up to date |
| wasm-bindgen | ^0 | 0.2.115 | up to date |
| wasm-bindgen-futures | ^0 | 0.4.65 | up to date |
| web-sys | ^0 | 0.3.92 | up to date |
| windows | ^0 | 0.62.2 | up to date |
(5 total, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| axum | ^0 | 0.8.8 | up to date |
| rand | ^0 | 0.10.0 | up to date |
| rayon | ^1 | 1.11.0 | up to date |
| tokio ⚠️ | ^1 | 1.50.0 | maybe insecure |
| tower | ^0 | 0.5.3 | up to date |
chrono: Potential segfault in `localtime_r` invocationsUnix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.
No workarounds are known.
tokio: reject_remote_clients Configuration corruptionOn Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.
This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.
The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.
Ensure that pipe_mode is set first after initializing a ServerOptions. For example:
let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);
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.