Inability of ArchController
to enable disabled hookstemplate
#82
Labels
bug
Something isn't working
downgraded by judge
Judge downgraded the risk level of this issue
duplicate-50
edited-by-warden
grade-b
QA (Quality Assurance)
Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax
🤖_11_group
AI based duplicate group recommendation
sufficient quality report
This report is of sufficient quality
Lines of code
https://github.com/code-423n4/2024-08-wildcat/blob/fe746cc0fbedc4447a981a50e6ba4c95f98b9fe1/src/HooksFactory.sol#L201-L208
https://github.com/code-423n4/2024-08-wildcat/blob/fe746cc0fbedc4447a981a50e6ba4c95f98b9fe1/src/HooksFactory.sol#L297-L299
Vulnerability details
Proof of Concept
In the current implementation of the Hookfactory contract
ArchController
, the owner can disable hook templates using thedisableHooksTemplate()
function, but there is no method provided to re-enable previously disabled hooks. This can create operational inefficiencies, forcing the owner to create new hook templates whenever they need to re-enable a previously disabled one.Relevant Code Snippet:
The current function only allows disabling hook templates:
Referencing the last audit- code-423n4/2023-10-wildcat-findings#431.
A function to reenable disabled hooks should be created.
Recommended Mitigation Steps
To resolve this, the
ArchController
should include a function to enable previously disabled hook templates. Below is a recommended implementation for theenableHooksTemplate()
function.The text was updated successfully, but these errors were encountered: