The BoostController#delegateBoost() does not validate whether the to address (the recipient of the delegation) is a supported pool. Since the protocol assumes that boost allocations are intended for registered pools, this oversight allows users to delegate their boost to arbitrary addresses, potentially leading to manipulation of boost mechanics or misallocation of rewards.
There's only zero address check for to(pool address). So unsupported pool address can receive a boost delegation.
Boosts can be sent to non-pool addresses, leading to misallocation and attempt to transfer boost benefits outside the system.
The contract assumes boosts only affect supported pools, but this is no longer enforced.
manual
Add a validation check in delegateBoost():
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.