The executeTransaction function incorrectly marks a transaction as executed before ensuring that the transaction was successfully processed. If the transaction fails, it remains permanently marked as executed, preventing any future attempts to execute it again.
The function contains the following flawed logic:
The transaction is marked as executed before attempting execution.
If the .call{value: txn.value}("")
fails (due to out-of-gas, recipient rejecting Ether, or other failures), the transaction remains in a "failed but executed" state.
Since txn.executed = true
, it can never be retried, resulting in a locked transaction.
Funds may become stuck: If the transaction fails, the contract prevents retrying it, meaning owners cannot resend the funds.
Multi-sig execution failure: The contract requires approvals from multiple owners, but a failure in execution means the intended recipient never receives the funds, yet the transaction is considered "processed."
Loss of funds usability: If a transaction was meant to transfer critical funds (e.g., payroll, treasury management), its failure can block further execution attempts, disrupting operations.
Manual code review
Modify the function to mark txn.executed = true;
only after ensuring the transaction succeeds.
Please read the CodeHawks documentation to know which submissions are valid. If you disagree, provide a coded PoC and explain the real likelyhood and the detailed impact on the mainnet without any supposition (if, it could, etc) to prove your point.
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.