Reentrancy flaw in the refund() function.
-The refund() function uses the nonReentrant() modifier, but it's incorrectly implemented as the locked variable is set as false, failing to prevent reentrant calls.
-Due to this inaccurate implementation, the contract is vulnerable to potential reentrancy attacks.
-Critical security flaw that could allow an attacker to drain funds from the contract.
-Large financial losses could occur.
Static code analysis, Automated audit tools
Correct the implementation of nonReentrant() modifier ensuring that locked variable is set to true before the function call.
Adopt proper mitigation techniques against reentrancy attacks.
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.