The contract does not validate that the organizer address is nonzero when calling setOrganizer or in the constructor. If the owner sets the organizer to the zero address, all organizer-only functions become permanently unusable, bricking core contract functionality such as configuring passes, creating performances, and managing memorabilia.
Likelihood:
The owner can accidentally or maliciously set the organizer to the zero address at any time.
This can occur during deployment or later via setOrganizer.
Impact:
All organizer-only functions revert forever, making the contract unusable for its intended purpose.
The project and its users are permanently locked out of critical features.
If the organizer is set to the zero address, any call to an organizer-only function will revert, bricking the contract’s main features.
To prevent this, always validate that the organizer address is not zero in both the constructor and setOrganizer:
Owner/admin is trusted / Zero address check - Informational
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.