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.
signatory(11 total, 9 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| clear_on_drop | ^0.2 | 0.2.5 | up to date |
| ed25519-dalek ⚠️ | ^0.8 | 2.1.1 | out of date |
| generic-array ⚠️ | ^0.9 | 1.0.0 | out of date |
| lazy_static | ^1 | 1.4.0 | up to date |
| rand | ^0.5 | 0.8.5 | out of date |
| ring | ^0.13 | 0.17.8 | out of date |
| secp256k1 | ^0.10 | 0.29.0 | out of date |
| sha2 | ^0.7 | 0.10.8 | out of date |
| sodiumoxide ⚠️ | ^0.1 | 0.2.7 | out of date |
| untrusted | ^0.6 | 0.9.0 | out of date |
| yubihsm | ^0.14 | 0.42.1 | out of date |
(1 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| criterion | ^0.2 | 0.5.1 | out of date |
sodiumoxide: generichash::Digest::eq always return truePartialEq implementation for generichash::Digest has compared itself to itself.
Digest::eq always returns true and Digest::ne always returns false.
generic-array: arr! macro erases lifetimesAffected versions of this crate allowed unsoundly extending
lifetimes using arr! macro. This may result in a variety of
memory corruption scenarios, most likely use-after-free.
ed25519-dalek: Double Public Key Signing Function Oracle Attack on `ed25519-dalek`Versions of ed25519-dalek prior to v2.0 model private and public keys as
separate types which can be assembled into a Keypair, and also provide APIs
for serializing and deserializing 64-byte private/public keypairs.
Such APIs and serializations are inherently unsafe as the public key is one of
the inputs used in the deterministic computation of the S part of the signature,
but not in the R value. An adversary could somehow use the signing function as
an oracle that allows arbitrary public keys as input can obtain two signatures
for the same message sharing the same R and only differ on the S part.
Unfortunately, when this happens, one can easily extract the private key.
Revised public APIs in v2.0 of ed25519-dalek do NOT allow a decoupled
private/public keypair as signing input, except as part of specially labeled
"hazmat" APIs which are clearly labeled as being dangerous if misused.