@chainsafe/lodestar
Affected
- introduced
0, fixed0.36.0(semver)
Fixed versions
0.36.0
Fix
- Fixed version
0.36.0npm install @chainsafe/[email protected]
Advisory
Also known as: CVE-2022-29219
AttesterSlashing number overflow
Impact
Possible consensus split given maliciously-crafted AttesterSlashing or ProposerSlashing being included on-chain.
Since we represent uint64 values as native javascript numbers, there is an issue when those variables with large (greater than 2^53) uint64 values are included on chain. In those cases, Lodestar may view _valid_ AttesterSlashing or ProposerSlashing as _invalid_, due to rounding errors in large number values. This causes a consensus split, where Lodestar nodes are forked away from the main network.
Similarly Lodestar may consider _invalid_ ProposerSlashing as _valid_, thus including in proposed blocks that will be considered invalid by the network.
Patches
https://github.com/ChainSafe/lodestar/pull/3977
Workarounds
Use BigInt to represent Slot and Epoch values in AttesterSlashing and ProposerSlashing objects. BigInt is too slow to be used in all Slot and Epoch cases, so we will carefully use BigInt just where necessary for consensus.
High Basis: The source's own band: HIGH
0, fixed 0.36.0 (semver)0.36.0
0.36.0npm install @chainsafe/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0