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 minmon

Dependencies

(21 total, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 toml^1.11.1.3+spec-1.1.0up to date
 reqwest^0.130.13.4up to date
 tokio^1.521.53.1up to date
 libsystemd^0.70.7.2up to date
 systemd-journal-logger^2.22.2.2up to date
 serde^1.01.0.229up to date
 nix^0.310.31.3up to date
 log^0.40.4.33up to date
 env_logger^0.110.11.11up to date
 async-trait^0.10.1.91up to date
 text_placeholder^0.50.5.1up to date
 chrono ⚠️^0.40.4.45maybe insecure
 lettre ⚠️^0.110.11.22maybe insecure
 sensors^0.20.2.2up to date
 rand^0.100.10.2up to date
 bollard^0.210.21.0up to date
 dasp_ring_buffer^0.110.11.0up to date
 num-bigint^0.40.5.1out of date
 num-integer^0.10.1.46up to date
 cron^0.160.17.0out of date
 regex^1.121.13.1up to date

Dev dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 mockall^0.140.15.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

lettre: TLS hostname verification disabled when using Boring TLS backend

RUSTSEC-2026-0141

An 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).