This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate serde-xrpl

Dependencies

(8 total, 2 outdated)

CrateRequiredLatestStatus
 bs58^0.4.00.5.1out of date
 hex^0.4.30.4.3up to date
 hex-literal^0.3.41.1.0out of date
 lazy_static^1.4.01.5.1up to date
 num-traits^0.2.140.2.19up to date
 rust_decimal^1.19.01.43.0up to date
 serde^1.0.1331.0.229up to date
 serde_json^1.0.741.0.154up to date

Crate xrpl-rs

Dependencies

(26 total, 13 outdated, 1 insecure)

CrateRequiredLatestStatus
 tokio^11.54.1up to date
 tokio-test^0.4.20.4.6up to date
 serde^1.0.1261.0.229up to date
 serde_json^1.0.641.0.154up to date
 reqwest^0.11.30.13.5out of date
 url^2.2.22.5.9up to date
 websocket^0.26.20.27.1out of date
 futures^0.3.150.3.34up to date
 async-trait^0.1.500.1.92up to date
 log^0.4.140.4.35up to date
 lazy_static^1.4.01.5.1up to date
 hex-literal^0.3.41.1.0out of date
 bs58^0.4.00.5.1out of date
 hex^0.4.30.4.3up to date
 rust_decimal^1.19.01.43.0up to date
 serde-xrpl^0.1.20.1.2up to date
 secp256k1^0.21.00.33.1out of date
 sha256^1.0.31.6.0up to date
 sha2^0.10.00.11.1out of date
 ed25519^1.3.03.0.0out of date
 ed25519-dalek ⚠️^1.0.13.0.0insecure
 ripemd^0.1.00.2.0out of date
 simple_logger^2.1.05.2.0out of date
 tokio-tungstenite^0.17.10.30.0out of date
 serde_with^1.12.03.25.0out of date
 rand^0.8.50.10.4out 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.