You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 30, 2021. It is now read-only.
Since there is no explicit +1 limit on the nonce check used by ethermint, this results in transactions passing the antehandler checksum as long as they are greater than the node’s cached nonce. If the victim sends a very large nonce transaction, the attacker can replay the transaction.
Details and Root Cause:
First, we found some ground truths:
As long as the MsgEthereumTx is larger than the current node’s cache nonce, it will pass both noncecheck.
Signaturecheck uses the nonce field of the transaction itself, so transactions larger than the current cached nonce can still pass signaturecheck.
Thus, if a msg have a large nonce,then it can be replaied.
Steps to Exploit:
Suppose the victim sends a nonce that is much larger than the current node’s cache.
An attacker can replay this transaction.
The text was updated successfully, but these errors were encountered:
Vulnerability Overview:
Since there is no explicit +1 limit on the nonce check used by ethermint, this results in transactions passing the antehandler checksum as long as they are greater than the node’s cached nonce. If the victim sends a very large nonce transaction, the attacker can replay the transaction.
Details and Root Cause:
First, we found some ground truths:
As long as the MsgEthereumTx is larger than the current node’s cache nonce, it will pass both noncecheck.
Signaturecheck uses the nonce field of the transaction itself, so transactions larger than the current cached nonce can still pass signaturecheck.
Thus, if a msg have a large nonce,then it can be replaied.
Steps to Exploit:
Suppose the victim sends a nonce that is much larger than the current node’s cache.
An attacker can replay this transaction.
The text was updated successfully, but these errors were encountered: