ETHW confirms contract vulnerability exploit, dismisses replay assault claims

ETHW confirms contract vulnerability exploit, dismisses replay assault claims

by Jeremy

Submit-Ethereum Merge proof-of-work (PoW) chain ETHW has moved to quell claims that it had suffered an on-chain replay assault over the weekend.

Sensible contract auditing agency BlockSec flagged what it described as a replay assault that passed off on Sept. 16, by which attackers harvested ETHW tokens by replaying the decision knowledge of Ethereum’s proof-of-stake (PoS) chain on the forked Ethereum PoW chain.

In keeping with BlockSec, the foundation reason for the exploit was resulting from the truth that the Omni cross-chain bridge on the ETHW chain used outdated chainID and was not appropriately verifying the right chainID of the cross-chain message.

Ethereum’s Mainnet and check networks use two identifiers for various makes use of, specifically, a community ID and a series ID (chainID). Peer-to-peer messages between nodes make use of community ID, whereas transaction signatures make use of chainID. EIP-155 launched chainID as a method to forestall replay assaults between the ETH and Ethereum Basic (ETC) blockchains.

BlockSec was the primary analytics service to flag the replay assault and notified ETHW, which in flip shortly rebuffed preliminary claims {that a} replay assault had been carried out on-chain. ETHW made makes an attempt to inform Omni Bridge of the exploit on the contract degree:

Evaluation of the assault revealed that the exploiter began by transferring 200 WETH by way of the Omni bridge of the Gnosis chain earlier than replaying the identical message on the PoW chain, netting an additional 200ETHW. This resulted within the steadiness of the chain contract deployed on the PoW chain being drained.

Associated: Cross-chains within the crosshairs: Hacks name for higher protection mechanisms

BlockSec’s evaluation of the Omni bridge supply code confirmed that the logic to confirm chainID was current, however the verified chainID used within the contract was pulled from a price saved within the storage named unitStorage.

The staff defined that this was not the right chainID collected by way of the CHAINID opcode, which was proposed by EIP-1344 and exacerbated by the ensuing fork after the Ethereum Merge:

“That is most likely resulting from the truth that the code is kind of outdated (utilizing Solidity 0.4.24). The code works effective on a regular basis till the fork of the PoW chain.”

This allowed attackers to reap ETHW and probably different tokens owned by the bridge on the PoW chain and go on to commerce these on marketplaces itemizing the related tokens. Cointelegraph has reached out BlockSec to determine the worth extracted throughout the exploit.

Following Ethereum’s profitable Merge occasion which noticed the good contract blockchain transition from PoW to PoS, a gaggle of miners determined to proceed the PoW chain by way of a tough fork.