The root cause is that there is no zero at risk check-in the constructor.
impact would be if the user deploys the contract with the zero address or the zero two connect address, he wouldn't... and he wouldn't... and if he wouldn't realize that, so it will cause a lot of impact and, you know, will break the whole system.
No zero address checks in constructor
Immutables set at deployment can never be changed — wrong address bricks protocol forever// Root cause in the codebase with @> marks to highlight the relevant section
Likelihood:
Low
Impact:
impact would be if the user deploys the contract with the zero address or the zero two connect address, he wouldn't... and he wouldn't... and if he wouldn't realize that, so it will cause a lot of impact and, you know, will break the whole system.
Add zero address checks at the beginning of the constructor:
The contest is live. Earn rewards by submitting a finding.
Submissions are being reviewed by our AI judge. Results will be available in a few minutes.
View all submissionsThe contest is complete and the rewards are being distributed.