Missing nonce in the EIP-712 signature scheme means signatures remain valid indefinitely and cannot be invalidated by the signer after creation.
EIP-712 signatures for delegated claims should include a nonce to ensure each signature can only be used once and becomes invalid after use. This prevents replay attacks and gives signers control over signature validity.
The MESSAGE_TYPEHASH and signature generation do not include a nonce, meaning signatures remain valid indefinitely and cannot be invalidated by the signer.
Likelihood:MEDIUM
Reason 1 :Exposed signatures from failed transactions or logs can be reused
Reason 2 : Signers cannot revoke signatures once created
Impact:MEDIUM
Impact 1:Reduced security compared to standard EIP-712 implementations
Impact 2: Signatures remain valid even if signer wants to cancel
This test demonstrates that once Alice signs a claim message, she has no way to invalidate it. Even if she changes her mind or the signature is leaked, anyone holding the signature can use it to claim on her behalf at any future time.
Add a nonce mapping and include it in the message hash. Increment the nonce after each claim to ensure old signatures become invalid. This follows standard EIP-712 best practices for signature security.
The contest is live. Earn rewards by submitting a finding.
Submissions are being reviewed by our AI judge. Results will be available in a few minutes.
View all submissionsThe contest is complete and the rewards are being distributed.