According to the current implementation of the setUpdateWeightRunnerAddress
if address (0) is passed as _updateWeightRunner
to the function, possibly due to human error, the system will behave unpredictably or enter a broken state
If the admin mistakenly passed address(0) as _updateWeightRunner
if updateWeightRunner
is use to point out to an important contract or responsible for executing some important actions this means the system will no longer be able to interact with that functionality
Unintentional Disabling:
If the admin mistakenly sets address(0), they could disable key functionality.
Broken Logic:
Other parts of the system depending on updateWeightRunner
would break or misbehave, leading to the inconsistent or incorrect system behavior.
Manual review
Add a validation that prevents the setting of updateWeightRunner
to address(0)
Please read the CodeHawks documentation to know which submissions are valid. If you disagree, provide a coded PoC and explain the real likelyhood and the detailed impact on the mainnet without any supposition (if, it could, etc) to prove your point.
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.