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.
sputnikvm(11 total, 5 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| digest | ^0.6 | 0.10.7 | out of date |
| etcommon-bigint | ^0.2 | 0.2.10 | up to date |
| etcommon-block | ^0.5 | 0.5.2 | up to date |
| etcommon-block-core | ^0.3 | 0.3.1 | up to date |
| etcommon-rlp | ^0.2 | 0.2.5 | up to date |
| libsecp256k1 ⚠️ | ^0.1 | 0.7.1 | out of date |
| log | ^0.4 | 0.4.21 | up to date |
| ripemd160 | ^0.6 | 0.10.0 | out of date |
| secp256k1-plus | ^0.5 | 0.5.7 | up to date |
| sha2 | ^0.6 | 0.10.8 | out of date |
| sha3 | ^0.6 | 0.10.8 | out of date |
(1 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| etcommon-hexutil | ^0.2 | 0.2.4 | up to date |
libsecp256k1: Flaw in Scalar::check_overflow allows side-channel timing attackVersions of libsecp256k1 prior to 0.3.1 did not execute
Scalar::check_overflow in constant time.
This allows an attacker to potentially leak information via a timing attack.
The flaw was corrected by modifying Scalar::check_overflow to execute in constant time.
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.