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.
volo-thrift(19 total, 3 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1 | 1.0.102 | up to date |
| bytes ⚠️ | ^1 | 1.11.1 | maybe insecure |
| chrono ⚠️ | ^0.4 | 0.4.44 | maybe insecure |
| futures | ^0.3 | 0.3.32 | up to date |
| fxhash | ^0.2 | 0.2.1 | up to date |
| lazy_static | ^1 | 1.5.0 | up to date |
| linked-hash-map | ^0.5 | 0.5.6 | up to date |
| linkedbytes | ^0.1 | 0.1.16 | up to date |
| metainfo | ^0.7 | 0.7.14 | up to date |
| motore | ^0.4 | 0.4.1 | up to date |
| num_enum | ^0.7 | 0.7.6 | up to date |
| parking_lot | ^0.12 | 0.12.5 | up to date |
| paste | ^1 | 1.0.15 | up to date |
| pilota | ^0.10 | 0.13.1 | out of date |
| pin-project | ^1 | 1.1.11 | up to date |
| thiserror | ^1 | 2.0.18 | out of date |
| tokio ⚠️ | ^1 | 1.51.1 | maybe insecure |
| tracing | ^0.1 | 0.1.44 | up to date |
| volo | ^0.9 | 0.12.3 | out of 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.