The createNewDAOMembership() function does not validate that maxMembers is greater than zero. This allows the creation of DAOs with maxMembers set to zero, which can prevent any users from joining the DAO and create administrative challenges, as the DAO cannot be easily managed or deleted.
In the createNewDAOMembership function, the following line checks that the sum of tier amounts does not exceed maxMembers:
However, there is no check to ensure that daoConfig.maxMembers is greater than zero. This omission allows a user to create a DAO with maxMembers set to zero, effectively locking the DAO and preventing any memberships from being issued.
A DAO with maxMembers set to zero cannot have any members, effectively locking the DAO and rendering it unusable.
The DAO cannot be easily managed or deleted, potentially leading to clutter
manual review
Ensure that maxMembers is greater than zero when creating a new DAO.
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.