The contract sends Ether to an external address without a re-entrancy guard.
Though the contract does not directly update its state before making the external call to transfer Ether, it's a good practice to use a re-entrancy guard to prevent any future issues that could make it vulnerable to re-entrancy attacks.
The most common one is Openzeppelin reentrancy guard.
potentially allow for re-entrancy attacks if the contract state is modified in the future before the external call.
Manual code review
Implement a re-entrancy guard using OpenZeppelin's ReentrancyGuard
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.