This project contains known security vulnerabilities. Find detailed information at the bottom.
sp-core(37 total, 24 outdated, 2 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| base58 | ^0.1.0 | 0.2.0 | out of date |
| blake2-rfc | ^0.2.18 | 0.2.18 | up to date |
| byteorder | ^1.3.2 | 1.5.0 | up to date |
| parity-scale-codec | ^2.0.0 | 3.7.5 | out of date |
| dyn-clonable | ^0.9.0 | 0.9.2 | up to date |
| ed25519-dalek ⚠️ | ^1.0.1 | 3.0.0 | insecure |
| futures | ^0.3.1 | 0.3.34 | up to date |
| hash-db | ^0.15.2 | 0.16.0 | out of date |
| hash256-std-hasher | ^0.15.2 | 0.15.2 | up to date |
| hex | ^0.4 | 0.4.3 | up to date |
| impl-serde | ^0.3.0 | 0.5.0 | out of date |
| lazy_static | ^1.4.0 | 1.5.0 | up to date |
| libsecp256k1 ⚠️ | ^0.3.2 | 0.7.2 | insecure |
| log | ^0.4.11 | 0.4.34 | up to date |
| merlin | ^2.0 | 3.0.0 | out of date |
| num-traits | ^0.2.8 | 0.2.19 | up to date |
| parity-util-mem | ^0.9.0 | 0.12.0 | out of date |
| parking_lot | ^0.11.1 | 0.12.5 | out of date |
| primitive-types | ^0.9.0 | 0.14.0 | out of date |
| rand | ^0.7.3 | 0.10.3 | out of date |
| regex | ^1.4.2 | 1.13.1 | up to date |
| schnorrkel | ^0.9.1 | 0.11.5 | out of date |
| secrecy | ^0.7.0 | 0.10.3 | out of date |
| serde | ^1.0.101 | 1.0.229 | up to date |
| sha2 | ^0.9.2 | 0.11.0 | out of date |
| sp-debug-derive | ^3.0.0 | 15.0.0 | out of date |
| sp-externalities | ^0.9.0 | 0.34.0 | out of date |
| sp-runtime-interface | ^3.0.0 | 37.0.0 | out of date |
| sp-std | ^3.0.0 | 14.0.0 | out of date |
| sp-storage | ^3.0.0 | 25.0.0 | out of date |
| substrate-bip39 | ^0.4.2 | 0.6.1 | out of date |
| thiserror | ^1.0.21 | 2.0.21 | out of date |
| tiny-bip39 | ^0.8 | 2.0.0 | out of date |
| tiny-keccak | ^2.0.1 | 2.0.2 | up to date |
| twox-hash | ^1.5.0 | 2.1.4 | out of date |
| wasmi | ^0.6.2 | 2.0.0 | out of date |
| zeroize | ^1.2.0 | 1.9.0 | up to date |
libsecp256k1: libsecp256k1 allows overflowing signatureslibsecp256k1 accepts signatures whose R or S parameter is larger than the secp256k1 curve order, which differs from other implementations. This could lead to invalid signatures being verified.
The error is resolved in 0.5.0 by adding a check_overflow flag.
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.