Hook or callback functions are expected to be invoked only by the trusted pool manager as part of normal protocol execution.
Callback functions lack sender validation, allowing arbitrary external callers to trigger internal state changes without a legitimate pool action.
Likelihood:
Occurs whenever hook functions are externally callable
Requires no special permissions or timing assumptions
Impact:
Attackers can manipulate internal protection state
Undermines anti-bot, fee, or cooldown logic
Restrict hook execution to the trusted pool manager.
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.
The contest is complete and the rewards are being distributed.