PeckShield: security concerns with ethereum Parity client that could accidentally cause the main network to 'fork'

According to BlockBeats, PeckShield security researchers found that due to a flaw in the ethereum Parity client, when it received a problem block, the next legal block with the same hash would not be processed. To be specific: an attacker can send a legitimate header+ an illegal body to the Parity client, so that the subsequent legitimate block header+body is filtered by the Partiy client but can be received by clients such as geth, potentially causing an accidental "fork" in the main Ethernet network. The Parity client currently accounts for 22.08% of ethereum's main network and is mainly used at related nodes such as mine pools and exchanges. PeckShield security personnel recommend that the pool and exchange nodes migrate to the geth client as soon as possible, while appropriately increasing the number of block confirmations.

Welcome to join the official BlockBeats community:

Telegram Subscription Group: https://t.me/theblockbeats

Telegram Discussion Group: https://t.me/BlockBeats_App

Official Twitter Account: https://twitter.com/BlockBeatsAsia