Deps.rs

near-crypto 0.12.0

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

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

(20 total, 11 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 arrayref^0.30.3.9up to date
 blake2^0.9.10.10.6out of date
 borsh^0.91.5.7out of date
 bs58^0.40.5.1out of date
 c2-chacha^0.30.3.3up to date
 curve25519-dalek ⚠️^34.1.3out of date
 deepsize^0.2.00.2.0up to date
 derive_more^0.99.92.0.1out of date
 ed25519-dalek ⚠️^12.1.1out of date
 libc^0.20.2.174up to date
 near-account-id^0.12.01.1.2out of date
 once_cell^1.5.21.21.3up to date
 parity-secp256k1^0.7N/Aup to date
 primitive-types^0.100.13.1out of date
 rand^0.70.9.1out of date
 rand_core^0.50.9.3out of date
 serde^11.0.219up to date
 serde_json^11.0.140up to date
 subtle^2.22.6.1up to date
 thiserror^12.0.12out of date

Dev dependencies

(2 total, 2 outdated)

CrateRequiredLatestStatus
 hex-literal^0.21.0.0out of date
 sha2>=0.8, <0.100.10.9out of 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.

curve25519-dalek: Timing variability in `curve25519-dalek`'s `Scalar29::sub`/`Scalar52::sub`

RUSTSEC-2024-0344

Timing variability of any kind is problematic when working with potentially secret values such as elliptic curve scalars, and such issues can potentially leak private keys and other secrets. Such a problem was recently discovered in curve25519-dalek.

The Scalar29::sub (32-bit) and Scalar52::sub (64-bit) functions contained usage of a mask value inside a loop where LLVM saw an opportunity to insert a branch instruction (jns on x86) to conditionally bypass this code section when the mask value is set to zero as can be seen in godbolt:

A similar problem was recently discovered in the Kyber reference implementation:

https://groups.google.com/a/list.nist.gov/g/pqc-forum/c/hqbtIGFKIpU/m/cnE3pbueBgAJ

As discussed on that thread, one portable solution, which is also used in this PR, is to introduce a volatile read as an optimization barrier, which prevents the compiler from optimizing it away.

The fix can be validated in godbolt here:

The problem was discovered and the solution independently verified by Alexander Wagner [email protected] and Lea Themint [email protected] using their DATA tool:

https://github.com/Fraunhofer-AISEC/DATA