Issue: The maxMembers
value is only enforced during the initial DAO creation and not consistently validated across other functions. While some parts of the contract validate the maximum member limit, it’s not consistently enforced in tier upgrades or other operations.
impact: Exceeding the maxMembers
could lead to an overflow of members within a DAO, which can disrupt operations and cause unintended behavior.
maxMembers
is only validated in createNewDAOMembership
but not consistently enforced during joinDAO
and upgradeTier
. This oversight allows an attacker to bypass maxMembers
and inflate the membership count beyond intended limits.
MembershipFactory.sol
:
joinDAO
does not enforce maxMembers
:
A user joins a DAO repeatedly, inflating the membership count.
Add maxMembers
validation in joinDAO
and upgradeTier
.
POC:
Tools used : VSC, GIthub
Recommendation: Add validation in joinDAO
and upgradeTier
functions to ensure that maxMembers
is enforced consistently, and restrict the total number of members across tiers.
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.