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, 2 possibly insecure)

CrateRequiredLatestStatus
 tokio^1.361.41.1up to date
 hyper^11.5.1up 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.21up to date
 colored^22.1.0up to date
 toml^0.80.8.19up to date
 tracing^0.10.1.40up to date
 tracing-subscriber^0.30.3.18up to date
 bytes^1.81.8.0up to date
 urlencoding^22.1.3up to date
 tokio-util^0.70.7.12up to date
 futures-util^0.30.3.31up to date
 regex^1.71.11.1up to date
 serde^11.0.215up to date
 lazy_static^11.5.0up to date
 chrono ⚠️^0.40.4.38maybe insecure
 log^0.40.4.22up to date
 rustls ⚠️^0.230.23.18maybe insecure
 tokio-rustls^0.260.26.0up 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::ConnectionCommon::complete_io` could fall into an infinite loop based on network input

RUSTSEC-2024-0336

If a close_notify alert is received during a handshake, complete_io does not terminate.

Callers which do not call complete_io are not affected.

rustls-tokio and rustls-ffi do not call complete_io and are not affected.

rustls::Stream and rustls::StreamOwned types use complete_io and are affected.