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

(22 total, 2 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 tokio^1.451.48.0up to date
 hyper^11.8.1up to date
 http-body-util^0.10.1.3up to date
 hyper-util^0.10.1.18up to date
 walkdir^22.5.0up to date
 clap^44.5.53up to date
 colored^33.0.0up to date
 toml^0.80.9.8out of date
 tracing^0.10.1.43up to date
 tracing-subscriber ⚠️^0.30.3.22maybe insecure
 bytes^1.101.11.0up to date
 urlencoding^22.1.3up to date
 tokio-util^0.70.7.17up to date
 futures-util^0.30.3.31up to date
 regex^1.91.12.2up to date
 serde^11.0.228up to date
 lazy_static^11.5.0up to date
 chrono ⚠️^0.40.4.42maybe insecure
 log^0.40.4.28up to date
 rustls ⚠️^0.230.23.35maybe insecure
 tokio-rustls^0.260.26.4up to date
 netdev^0.350.39.0out of 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.

tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequences

RUSTSEC-2025-0055

Previous 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:

  • Manipulate terminal title bars
  • Clear screens or modify terminal display
  • Potentially mislead users through terminal manipulation

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.