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 nkeys

Dependencies

(12 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 byteorder^1.3.41.5.0up to date
 data-encoding^2.2.02.5.0up to date
 ed25519-dalek ⚠️^1.0.0-pre.22.1.1out of date
 env_logger^0.7.10.11.3out of date
 exitfailure^0.5.10.5.1up to date
 log^0.4.80.4.21up to date
 quicli^0.40.4.0up to date
 rand^0.7.30.8.5out of date
 signatory^0.18.10.27.1out of date
 signatory-dalek^0.18.1N/Aup to date
 structopt^0.3.110.3.26up to date
 term-table^1.2.01.3.2up to date

Security Vulnerabilities

ed25519-dalek: Double Public Key Signing Function Oracle Attack on `ed25519-dalek`

RUSTSEC-2022-0093

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.