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 bandurria

Dependencies

(22 total, 2 possibly insecure)

CrateRequiredLatestStatus
 log^0.40.4.29up to date
 clap^4.54.5.57up to date
 lazy_static^1.51.5.0up to date
 regex^1.111.12.3up to date
 serde^1.01.0.228up to date
 serde_derive^1.01.0.228up to date
 toml^0.90.9.11+spec-1.1.0up to date
 envsubst^0.20.2.1up to date
 sha2^0.100.10.9up to date
 hmac^0.120.12.1up to date
 hex^0.40.4.3up to date
 base64-url^3.03.0.2up to date
 linkify^0.100.10.0up to date
 validator^0.200.20.0up to date
 uuid^1.121.20.0up to date
 chrono ⚠️^0.40.4.43maybe insecure
 rocket^0.50.5.1up to date
 rocket_dyn_templates^0.20.2.0up to date
 rocket_db_pools^0.20.2.0up to date
 rustls ⚠️^0.230.23.36maybe insecure
 reqwest^0.130.13.2up to date
 lettre^0.110.11.19up 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.