Vulnerability	Vulnerable Version
H Buffer Overflow @chainsafe/lodestar is an A Typescript implementation of the beacon chain Affected versions of this package are vulnerable to Buffer Overflow. Possible consensus split given maliciously-crafted `AttesterSlashing` or `ProposerSlashing` being included on-chain. The library represents `uint64` values as native javascript `number`s, causing 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. 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 use `BigInt` only when necessary for consensus. How to fix Buffer Overflow? Upgrade `@chainsafe/lodestar` to version 0.36.0 or higher.	<0.36.0

Buffer Overflow

@chainsafe/lodestar is an A Typescript implementation of the beacon chain

Affected versions of this package are vulnerable to Buffer Overflow. Possible consensus split given maliciously-crafted AttesterSlashing or ProposerSlashing being included on-chain.

The library represents uint64 values as native javascript numbers, causing 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.

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 use BigInt only when necessary for consensus.

How to fix Buffer Overflow?

Upgrade @chainsafe/lodestar to version 0.36.0 or higher.

<0.36.0

Go back to all versions of this package