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 tmkms

Dependencies

(30 total, 17 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 abscissa^0.0.60.7.0out of date
 abscissa_derive^0.0.20.7.0out of date
 atomicwrites^0.20.4.3out of date
 byteorder^1.21.5.0up to date
 bytes^0.41.6.0out of date
 chrono ⚠️^0.40.4.37maybe insecure
 failure^0.10.1.8up to date
 failure_derive^0.10.1.8up to date
 hkdf^0.70.12.4out of date
 hmac^0.70.12.1out of date
 lazy_static^11.4.0up to date
 prost-amino^0.4.00.6.0out of date
 prost-amino-derive^0.4.00.6.1out of date
 rand_os^0.10.2.2out of date
 serde^11.0.197up to date
 serde_derive^11.0.197up to date
 serde_json^11.0.115up to date
 sha2^0.80.10.8out of date
 signal-hook^0.1.70.3.17out of date
 signatory^0.11.10.27.1out of date
 signatory-dalek^0.11N/Aup to date
 signatory-ledger-tm^0.11N/Aup to date
 signatory-secp256k1^0.11N/Aup to date
 subtle^22.5.0up to date
 subtle-encoding^0.30.5.1out of date
 tendermint^0.5.0-alpha10.35.0out of date
 tiny-bip39^0.61.0.0out of date
 wait-timeout^0.20.2.0up to date
 yubihsm^0.220.42.1out of date
 zeroize^0.51.7.0out of date

Dev dependencies

(2 total, 1 outdated)

CrateRequiredLatestStatus
 rand^0.60.8.5out of date
 tempfile^33.10.1up 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