Submission Details
Severity:
Functions calling contracts/addresses with transfer hooks are missing reentrancy guards
Summary
Vulnerability Details
Even if the function follows the best practice of check-effects-interaction,
not using a reentrancy guard when there may be transfer hooks will open the
users of this protocol up to
read-only reentrancies
with no way to protect against it, except by block-listing the whole protocol.
There is 1 instance of this issue:
success = IERC20(tokenCollateralAddress).transfer(to,amountCollateral) should use Reentrancy-Guard.
Impact
Tools Used
Recommendations
Using Reentrancy-Guard
when calling contracts/addresses with transfer hooks.
Prize pool breakdown
Total prize
15,000 USDC
nSLOC
23664 USDC / LOC
14,000 USDC
1,000 USDC
Live
The contest is live. Earn rewards by submitting a finding.
Appeals
This is your time to appeal against judgements on your submissions.
Appeals Review
Appeals are being carefully reviewed by our judges.