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.
sc-executor(21 total, 18 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| parity-scale-codec | ^1.3.4 | 3.6.12 | out of date |
| derive_more | ^0.99.2 | 0.99.17 | up to date |
| lazy_static | ^1.4.0 | 1.4.0 | up to date |
| libsecp256k1 ⚠️ | ^0.3.4 | 0.7.1 | out of date |
| log | ^0.4.8 | 0.4.21 | up to date |
| parity-wasm | ^0.41.0 | 0.45.0 | out of date |
| parking_lot | ^0.10.0 | 0.12.2 | out of date |
| sc-executor-common | ^0.8.0 | 0.33.0 | out of date |
| sc-executor-wasmi | ^0.8.0 | 0.22.0 | out of date |
| sc-executor-wasmtime | ^0.8.0 | 0.33.0 | out of date |
| sp-api | ^2.0.0 | 31.0.0 | out of date |
| sp-core | ^2.0.0 | 32.0.0 | out of date |
| sp-externalities | ^0.8.0 | 0.28.0 | out of date |
| sp-io | ^2.0.0 | 35.0.0 | out of date |
| sp-panic-handler | ^2.0.0 | 13.0.0 | out of date |
| sp-runtime-interface | ^2.0.0 | 27.0.0 | out of date |
| sp-serializer | ^2.0.0 | 5.0.0 | out of date |
| sp-trie | ^2.0.0 | 34.0.0 | out of date |
| sp-version | ^2.0.0 | 34.0.0 | out of date |
| sp-wasm-interface | ^2.0.0 | 21.0.0 | out of date |
| wasmi | ^0.6.2 | 0.31.2 | out of 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.