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.
httprs(22 total, 2 outdated, 4 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| tokio | ^1.45 | 1.50.0 | up to date |
| hyper | ^1 | 1.8.1 | up to date |
| http-body-util | ^0.1 | 0.1.3 | up to date |
| hyper-util | ^0.1 | 0.1.20 | up to date |
| walkdir | ^2 | 2.5.0 | up to date |
| clap | ^4 | 4.6.0 | up to date |
| colored | ^3 | 3.1.1 | up to date |
| toml | ^0.8 | 1.0.6+spec-1.1.0 | out of date |
| tracing | ^0.1 | 0.1.44 | up to date |
| tracing-subscriber ⚠️ | ^0.3 | 0.3.23 | maybe insecure |
| bytes ⚠️ | ^1.10 | 1.11.1 | maybe insecure |
| urlencoding | ^2 | 2.1.3 | up to date |
| tokio-util | ^0.7 | 0.7.18 | up to date |
| futures-util | ^0.3 | 0.3.32 | up to date |
| regex | ^1.9 | 1.12.3 | up to date |
| serde | ^1 | 1.0.228 | up to date |
| lazy_static | ^1 | 1.5.0 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.44 | maybe insecure |
| log | ^0.4 | 0.4.29 | up to date |
| rustls ⚠️ | ^0.23 | 0.23.37 | maybe insecure |
| tokio-rustls | ^0.26 | 0.26.4 | up to date |
| netdev | ^0.35 | 0.40.1 | 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.
rustls: rustls network-reachable panic in `Acceptor::accept`A bug introduced in rustls 0.23.13 leads to a panic if the received
TLS ClientHello is fragmented. Only servers that use
rustls::server::Acceptor::accept() are affected.
Servers that use tokio-rustls's LazyConfigAcceptor API are affected.
Servers that use tokio-rustls's TlsAcceptor API are not affected.
Servers that use rustls-ffi's rustls_acceptor_accept API are affected.
tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequencesPrevious versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:
In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.
This was patched in PR #3368 to escape ANSI control characters from user input.
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.