Submission Details
Severity:
Cross-chain signature replay attack
Summary
The signature issued by operator, can be replayed across different chains.
Vulnerability details
There is no chain.id in signed data. According to comments: L2 will have a similar mechanism for withdrawing tokens from L1 to L2. So same signature can be used for withdrawing.
/*
* @notice This is the function responsible for withdrawing tokens from L2 to L1.
* Our L2 will have a similar mechanism for withdrawing tokens from L1 to L2.
*/
Impact
As specified by the EIP4337 standard to prevent replay attacks ... the signature should depend on chain.id.
Tools used
Manual Review
Recommendations
Include chain.id in hashed data
Rewards breakdown
nSLOC
99This contest has a flat reward structure with the following payouts:
100 EXP
20 EXP
2 EXP
Live
The contest is live. Earn rewards by submitting a finding.
Appeals
This is your time to appeal against judgements on your submissions.
Appeals Review
Appeals are being carefully reviewed by our judges.