The AaveDIVAWrapper contract lacks an emergency stop(pause/unpause) mechanism to pause critical operations when vulnerabilities are detected in its integrated protocols (Aave V3 or DIVA) or its own logic. This violates the protocol’s own risk acknowledgment in the known issues section:
"Integration risk with both Aave V3 and DIVA Protocol - vulnerabilities in either protocol may affect AaveDIVAWrapper."
Impact Breakdown:
Unstoppable Exploits: If Aave V3 (upgradeable) introduces a breaking change or DIVA has a vulnerability.
Documented Risk Mitigation: The documentation explicitly warns about external integration risks but provides no operational safeguards to address them.
This directly threatens the system’s core invariant: "Assets deposited into DIVA Protocol pools generate yield safely via Aave V3."
Trigger: Aave V3 or DIVA suffers a critical bug.
Result:
AaveDIVAWrapper cannot pause operations leading to internal issues.
Protocol reserves and user funds are vulnerable.
Manual Review
Immediate Mitigation:
Integrate OpenZeppelin’s Pausable
and guard all state-changing functions
Governance Enhancement:
Restrict emergencyPause
to a multisig or DAO to prevent centralized abuse.
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.