Closed sherlock-admin3 closed 3 months ago
Invalid, there is no exploit here. Whitelisting/Blacklisting mechanism is only meant to be use for gauge pool creation
Any users can create gauge for pools with whitelisted tokens on one side. (Permissionless gauge creation) Otherwise, gauge for pools without whitelisted tokens can only be created by protoc
Minato7namikazi
Medium
unhandled case in the
whitelist
andblacklist
functionsVulnerability Detail
unhandled case in the
whitelist
andblacklist
functions:The bug here is that there's no mechanism to handle tokens that are part of existing pools when they are blacklisted. This can lead to a situation where:
This scenario could potentially allow deprecated or problematic tokens to remain active in the system, which might not be the intended behavior when blacklisting a token.
To address this issue, we should add functionality to handle existing pools when a token is blacklisted. So we should
Code Snippet
https://github.com/sherlock-audit/2024-06-velocimeter/blob/main/v4-contracts/contracts/Voter.sol#L301
Tool used
Manual Review