Impact
A vulnerable node can be made to consume very large amounts of memory when handling specially crafted p2p messages sent from an attacker node.
In order to carry out the attack, the attacker establishes a peer connections to the victim, and sends a malicious GetBlockHeadersRequest message with a count of 0, using the ETH protocol.
In descendants := chain.GetHeadersFrom(num+count-1, count-1), the value of count-1 is passed to the function GetHeadersFrom(number, count uint64) as parameter count. Due to integer overflow, UINT64_MAX value is then passed as the count argument to function GetHeadersFrom(number, count uint64). This allows an attacker to bypass maxHeadersServe and request all headers from the latest block back to the genesis block.
Patches
The fix has been included in geth version 1.13.15 and onwards.
The vulnerability was patched in: ethereum/go-ethereum#29534
Workarounds
No workarounds have been made public.
References
No more information is released at this time.
Credit
This issue was disclosed responsibly by DongHan Kim via the Ethereum bug bounty program. Thank you for your cooperation.
References
Impact
A vulnerable node can be made to consume very large amounts of memory when handling specially crafted p2p messages sent from an attacker node.
In order to carry out the attack, the attacker establishes a peer connections to the victim, and sends a malicious
GetBlockHeadersRequestmessage with acountof0, using theETHprotocol.In
descendants := chain.GetHeadersFrom(num+count-1, count-1), the value ofcount-1is passed to the functionGetHeadersFrom(number, count uint64)as parametercount. Due to integer overflow,UINT64_MAXvalue is then passed as thecountargument to functionGetHeadersFrom(number, count uint64). This allows an attacker to bypassmaxHeadersServeand request all headers from the latest block back to the genesis block.Patches
The fix has been included in geth version
1.13.15and onwards.The vulnerability was patched in: ethereum/go-ethereum#29534
Workarounds
No workarounds have been made public.
References
No more information is released at this time.
Credit
This issue was disclosed responsibly by DongHan Kim via the Ethereum bug bounty program. Thank you for your cooperation.
References