The smart contract is missing reentrancy guards when calling contracts/addresses with transfer hooks, potentially leading to read-only reentrancy attacks.
The functions in the smart contract that interact with contracts or addresses containing transfer hooks lack reentrancy guards. This omission could expose users of the protocol to read-only reentrancy attacks, creating a security risk.
The absence of reentrancy guards in functions with transfer hooks could allow attackers to exploit the contract's vulnerability. They may manipulate the flow of the contract, potentially leading to unauthorized read access or undesired behavior, jeopardizing user funds and data.
Manual Review
Implement reentrancy guards
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.