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 faktory

Dependencies

(25 total, 7 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.770.1.88up to date
 clap^4.4.104.5.38up to date
 chrono ⚠️^0.40.4.41maybe insecure
 derive_builder^0.12.00.20.2out of date
 fnv^1.0.51.0.7up to date
 hostname^0.30.4.1out of date
 pin-project^1.1.41.1.10up to date
 rand^0.80.9.1out of date
 serde^1.0.1861.0.219up to date
 serde_derive^1.01.0.219up to date
 serde_json^1.01.0.140up to date
 sha2^0.10.00.10.9up to date
 thiserror^1.0.302.0.12out of date
 tokio^1.35.11.45.0up to date
 tokio-native-tls^0.3.10.3.1up to date
 tokio-rustls^0.25.00.26.2out of date
 rustls-native-certs^0.7.10.8.1out of date
 tracing^0.10.1.41up to date
 url^22.5.4up to date
 semver^1.0.231.0.26up to date
 native-tls^0.2.40.2.14up to date
 num-bigint^0.4.20.4.6up to date
 oid-registry^0.6.10.8.1out of date
 openssl ⚠️^0.10.600.10.72maybe insecure
 rustls-pki-types^1.0.11.12.0up to date

Dev dependencies

(6 total, 1 outdated)

CrateRequiredLatestStatus
 rustls-pki-types^1.0.11.12.0up to date
 tokio^1.35.11.45.0up to date
 tokio-test^0.4.30.4.4up to date
 tokio-util^0.7.110.7.15up to date
 tracing-subscriber^0.3.180.3.19up to date
 x509-parser^0.15.10.17.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

openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`

RUSTSEC-2025-0022

When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.

In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).

The maintainers thank quitbug for reporting this vulnerability to us.