Open hats-bug-reporter[bot] opened 1 week ago
Non-issue is a expected behavior, because when you promote a SuperSafe to New rootSafe, the superSafe by definition have to be at least one children!!, so the if as you mention verify if the array of child safe is equal or less zero (not have children), and is not a superSafe and in this case can't promote to RootSafe, and revert the transactions with the error: NotAuthorizedUpdateNonSuperSafe()
so, is non-issue!!
Github username: -- Twitter username: SBSecurity_ Submission hash (on-chain): 0x6f1605ee79adeebcb5abdd118371fae970945d27bc037849c504d0c0c75bc4fc Severity: medium
Description: Description\ promoteRoot() is used to promote SAFEs to Root of an org. But only safes that have 0 children can become ROOTs which is unfair, because the actual ROOTs have children, why a SAFE with existing ones to cannot be promoted.
Attack Scenario\ If SAFE has 0 children and any of its ROOTs tries to promote him, promoteRoot() will fail, because of this check.
Attachments
Proof of Concept (PoC) File
Revised Code File (Optional) Allow even a safe with childs to become ROOT