Modules could maliciously revert on onUninstall
to stop the account from uninstalling a module.
This is an expressed concern in EIP-7595 security considerations. However, there is no fix to it in the current implementation (attestation registries seems to not handle it all)
The
onInstall
andonUninstall
functions on modules may lead to unexpected callbacks (e.g. reentrancy). Account implementations should consider this by implementing adequate protection routines. Furthermore, modules could maliciously revert on onUninstall to stop the account from uninstalling a module and removing it from the account.
Accounts become "stuck" with malicious modules. The possibilities are endless.
Modify MockHook::onUninstall
to include a revert:
Run forge test --mt test_UninstallHookModule_Success
, here is the expected output:
Foundry
Invalid, - hook logic is OOS - all other `onUninstall()` functions do not revert, so the hawk here is essentially introducing code logic that doesn't exist. - Known issue: > The security of Nexus smart accounts relies heavily on the modules used. Only secure and audited modules should be installed to maintain the overall security of the system.
Invalid, - hook logic is OOS - all other `onUninstall()` functions do not revert, so the hawk here is essentially introducing code logic that doesn't exist. - Known issue: > The security of Nexus smart accounts relies heavily on the modules used. Only secure and audited modules should be installed to maintain the overall security of the system.
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.