The protocol’s signature mechanism lacks an expiration, resulting in signatures that are valid indefinitely.
This oversight could allow a signed transaction to be executed at any future time, potentially exposing the signer to unintended
actions and security risks. Since the protocol currently requires the signer to execute a new transaction to invalidate the old
signature.
Once a user signs a transaction, that signature remains valid indefinitely. Any party in possession of the signature could execute it at any time,
until signer sign and execute another message but with deadline the singer will decide when the signature is not valid.
The executeMetaTransaction
uses nonce but this is not efficient because the nonce doesn't put deadline and signature can be execute any time.
Without an deadline
, users lack control over how long their signed transactions remain valid, leaving them vulnerable to unexpected future transactions.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.