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.

Crate httprs

Dependencies

(21 total, 1 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 tokio^1.381.44.0up to date
 hyper^11.6.0up to date
 http-body-util^0.10.1.2up to date
 hyper-util^0.10.1.10up to date
 walkdir^22.5.0up to date
 clap^44.5.32up to date
 colored^23.0.0out of date
 toml^0.80.8.20up to date
 tracing^0.10.1.41up to date
 tracing-subscriber^0.30.3.19up to date
 bytes^1.101.10.1up to date
 urlencoding^22.1.3up to date
 tokio-util^0.70.7.13up to date
 futures-util^0.30.3.31up to date
 regex^1.91.11.1up to date
 serde^11.0.219up to date
 lazy_static^11.5.0up to date
 chrono ⚠️^0.40.4.40maybe insecure
 log^0.40.4.26up to date
 rustls ⚠️^0.230.23.23maybe insecure
 tokio-rustls^0.260.26.2up to date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-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.

Workarounds

No workarounds are known.

References

rustls: rustls network-reachable panic in `Acceptor::accept`

RUSTSEC-2024-0399

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.