Closed code423n4 closed 1 year ago
0xSorryNotSorry marked the issue as primary issue
deanamiel marked the issue as sponsor disputed
This implies that the target contract has security vulnerabilities, signers should not vote for a proposal that calls a target with such vulnerabilities. Additionally, Axelar governance would not create a proposal on a vulnerable target contract.
berndartmueller marked the issue as unsatisfactory: Out of scope
Lines of code
https://github.com/code-423n4/2023-07-axelar/blob/2f9b234bb8222d5fbe934beafede56bfb4522641/contracts/cgp/governance/InterchainGovernance.sol#L68-L79
Vulnerability details
Impact
A malicious proposal can take over the contract address of the accepted proposal through self-destruct
Proof of Concept
This issue is regarding the Tornado cash hack, whereby the attacker deploys different contracts at the same address. If the proposal manages to have a self-destruct function inside the code, then they can destroy their proposed contract and create a malicious one with the same address.
Tornado Cash Hack - https://www.youtube.com/watch?v=whjRc4H-rAc&t=362s
Tools Used
Manual Review
Recommended Mitigation Steps
Not sure about the recommendation, but just be alert to check for the self-destruct function in all the proposals that come in
Assessed type
Other