Admin should be able to remove collections from the list, but removing works only if the collection is on the first or second position. (Only these two cases are covered in unit tests)
However, if the collection is in any other location, the transaction will run out of gas.
The vulnerability is present in _white_list_collection
it contains the loop that should go through the linked list, but it is missing a piece of code at the end of the loop when prev
element becomes the next
. So the same element is checked over and over again until the gas runs out.
Admin would not be able to remove collection from whitelist. In such scenarios, the protocol may suffer losses:
There are some technical difficulties in using such a collection or the collection exposes the protocol to some security issues.
This collection contains inappropriate content (offensive or illegal).
Legal problems or when collection is related to some frauds.
Low interest in collection.
Manual Review
Add the missing piece of code at the end of the loop.
Likelyhood: High, owner can only unwhitelist the 2 first collections. Impact: Medium/High, owner has to empty the list to remove any collection, and replace all the new ones.
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.