Summary: Blockhash’s wrong implementation can trigger a reorganization of the chain leading to consensus problems
Assigned configurations: All GETH versions up to 1.1.3 and 1.2.2. All ETH ETH versions 1.0.0.
Probability: Weak
Severity: AVERAGE
Impact: AVERAGE
Details: C ++ (ETH) and GO (GETH) customers have an erroneous implementation of an edge case in the Ethereum virtual machine, in particular the chain that blockhash uses use to recover blocks. This on -board case is very little likely to occur on a live network because it would only be triggered in certain types of chain reorganizations (a contract executing blockhash (n – 1) where n is the head of a non -canonical sub -chain which is not yet reorganized to become the canonical chain (better / longer) but which will be after the block).
Pyethereum is not affected.
Effects on the depth of reorganization of the expected chain: none
Repair actions taken by Ethereum: Hotfixs provision as below.
Geth:
App: Update Sudo Apt-Get then Sudo Apt-Get Upgrade
Brew: BREW UPDATE then breaststroke reinstall Ethereum
Window: Download the updated binary
Building from the source:
git fetch origin && git checkout origin/master
ETH:
App::
