Deps.rs

near-crypto 0.16.1

[![dependency status](https://deps.rs/crate/near-crypto/0.16.1/status.svg)](https://deps.rs/crate/near-crypto/0.16.1)

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 near-crypto

Dependencies

(19 total, 11 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 blake2^0.9.10.10.6out of date
 borsh^0.10.21.5.0out of date
 bs58^0.40.5.1out of date
 c2-chacha^0.30.3.3up to date
 curve25519-dalek^34.1.2out of date
 derive_more^0.99.90.99.17up to date
 ed25519-dalek ⚠️^12.1.1out of date
 hex^0.4.20.4.3up to date
 near-account-id^0.16.11.0.0out of date
 near-config-utils^0.16.10.22.0out of date
 once_cell^1.13.11.19.0up to date
 primitive-types^0.100.12.2out of date
 rand^0.70.8.5out of date
 secp256k1^0.240.29.0out of date
 serde^1.0.1361.0.202up to date
 serde_json^1.0.681.0.117up to date
 near-stdx^0.16.00.22.0out of date
 subtle^2.22.5.0up to date
 thiserror^1.0.301.0.61up to date

Dev dependencies

(3 total, 1 outdated)

CrateRequiredLatestStatus
 hex-literal^0.20.4.1out of date
 sha2^0.100.10.8up to date
 tempfile^3.33.10.1up 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.