The function setVaultEngine
does not include a check to ensure the engine
address is not address(0)
.
If an invalid (zero) address is set, it could result in undefined or broken functionality when interacting with the vault.
This issue could arise due to a misconfiguration or an intentional attack to disrupt vault operations.
Setting the engine
to address(0)
could disable vault functionalities, making it impossible to process transactions or interact with the vault as intended.
This could lead to funds becoming inaccessible or operations being halted if the vault relies on the engine
for execution.
An attacker or a careless admin could exploit this issue to disrupt the vault's normal operation.
leads to inaccessibility of important protocol vault functionalities. Setting the engine
to address(0)
can disable vault functionalities, making it impossible to process transactions or interact with the vault as intended.
Manual Review
Implement a require statement to prevent setting engine
to address(0)
:
This simple check ensures that only valid, non-zero addresses can be assigned to the vaultEngine
, preventing unintended or malicious disruptions.
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.