Skip to content

Latest commit

 

History

History
46 lines (26 loc) · 1.46 KB

File metadata and controls

46 lines (26 loc) · 1.46 KB

Mini Navy Dachshund

Medium

Attacker will Disrupt Batch Signer Registration through Front-running

Summary

Attackers can front-run claimSignersFor transactions by registering individual signers first through claimSignerFor, causing the batch registration to fail.

Root Cause

function claimSignerFor : https://github.com/sherlock-audit/2024-11-hats-protocol/blob/49de29508904e95b3cfaaf27d2e76c527429c019/hats-zodiac/src/HatsSignerGate.sol#L215 function claimSignersFor : https://github.com/sherlock-audit/2024-11-hats-protocol/blob/49de29508904e95b3cfaaf27d2e76c527429c019/hats-zodiac/src/HatsSignerGate.sol#L227

Attackers can front-run claimSignersFor by calling claimSignerFor.

Internal pre-conditions

No response

External pre-conditions

No response

Attack Path

1.Legitimate user creates a transaction to call claimSignersFor with multiple signers 2.Attacker monitors mempool and sees this transaction 3.Attacker extracts one of the signer addresses and corresponding hat ID from the transaction data 4.Attacker front-runs with a higher gas price, calling claimSignerFor for one of the signers 5.The legitimate user's claimSignersFor transaction executes but reverts because one signer is already registered 6.The entire batch registration fails

Impact

The legitimate users cannot execute batch signer registration efficiently. This results in increased gas costs from failed transactions.

PoC

No response

Mitigation

No response