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.
prosa-utils(26 total, 4 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| base64 | ^0.22 | 0.22.1 | up to date |
| bytes ⚠️ | ^1 | 1.11.1 | maybe insecure |
| chrono ⚠️ | ^0.4 | 0.4.44 | maybe insecure |
| flate2 | ^1 | 1.1.9 | up to date |
| glob | ^0.3 | 0.3.3 | up to date |
| hex | ^0.4 | 0.4.3 | up to date |
| http-body-util | ^0.1 | 0.1.3 | up to date |
| hyper | ^1 | 1.9.0 | up to date |
| hyper-util | ^0.1 | 0.1.20 | up to date |
| log | ^0.4 | 0.4.29 | up to date |
| openssl ⚠️ | ^0.10 | 0.10.77 | maybe insecure |
| opentelemetry | ^0.31.0 | 0.31.0 | up to date |
| opentelemetry-appender-tracing | ^0.31.0 | 0.31.1 | up to date |
| opentelemetry-otlp | ^0.31.0 | 0.31.1 | up to date |
| opentelemetry-prometheus | ^0.31.0 | 0.31.0 | up to date |
| opentelemetry-stdout | ^0.31.0 | 0.31.0 | up to date |
| opentelemetry_sdk | ^0.31.0 | 0.31.0 | up to date |
| prometheus | ^0.14 | 0.14.0 | up to date |
| serde | ^1 | 1.0.228 | up to date |
| serde_yaml | ^0.9 | 0.9.34+deprecated | up to date |
| thiserror | ^2 | 2.0.18 | up to date |
| tokio ⚠️ | ^1 | 1.52.1 | maybe insecure |
| tracing-core | ^0.1 | 0.1.36 | up to date |
| tracing-opentelemetry | ^0.32.1 | 0.32.1 | up to date |
| tracing-subscriber | >=0.3.20, <0.4 | 0.3.23 | up to date |
| url | ^2 | 2.5.8 | up to date |
(2 total, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| tokio ⚠️ | ^1 | 1.52.1 | maybe insecure |
| tokio-openssl | ^0.6 | 0.6.5 | 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);
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.