Advisory

GHSA-cvj7-5f3c-9vg9

Also known as: CVE-2022-29219

Summary

AttesterSlashing number overflow

Details

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2022-05-24 22:21 UTC
Modified
2023-11-08 04:09 UTC

Affected packages and fixes

@chainsafe/lodestar

npm · All systems

Affected

  • introduced 0, fixed 0.36.0 (semver)

Fixed versions

0.36.0

Fix

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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences