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.
bandurria(22 total, 5 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| log | ^0.4 | 0.4.33 | up to date |
| clap | ^4.5 | 4.6.4 | up to date |
| lazy_static | ^1.5 | 1.5.0 | up to date |
| regex | ^1.11 | 1.13.1 | up to date |
| serde | ^1.0 | 1.0.229 | up to date |
| serde_derive | ^1.0 | 1.0.229 | up to date |
| toml | ^0.9 | 1.1.3+spec-1.1.0 | out of date |
| envsubst | ^0.2 | 0.2.1 | up to date |
| sha2 | ^0.10 | 0.11.0 | out of date |
| hmac | ^0.12 | 0.13.0 | out of date |
| hex | ^0.4 | 0.4.3 | up to date |
| base64-url | ^3.0 | 3.0.4 | up to date |
| linkify | ^0.10 | 0.11.0 | out of date |
| validator | ^0.20 | 0.21.0 | out of date |
| uuid | ^1.12 | 1.24.0 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.45 | maybe insecure |
| rocket | ^0.5 | 0.5.1 | up to date |
| rocket_dyn_templates | ^0.2 | 0.2.0 | up to date |
| rocket_db_pools | ^0.2 | 0.2.0 | up to date |
| rustls ⚠️ | ^0.23 | 0.23.42 | maybe insecure |
| reqwest | ^0.13 | 0.13.4 | up to date |
| lettre ⚠️ | ^0.11 | 0.11.22 | maybe insecure |
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.
lettre: TLS hostname verification disabled when using Boring TLS backendAn inverted-boolean bug in lettre's boring-tls integration silently
disables TLS hostname verification for callers using the default (strict)
configuration. An on-path attacker presenting any chain-valid certificate
for any domain can intercept SMTP submission, including PLAIN/LOGIN
credentials and message contents, against any lettre user built with the
boring-tls feature. Other TLS backends (native-tls, rustls) are
unaffected.
The bug was introduced in v0.10.1 and persists through v0.11.21 (latest).