20,000 USDC
View results
Submission Details
Severity: low

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 are 20 instances of this issue:

Impact

Tools Used

Recommendations

Using Reentrancy-Guard
when calling contracts/addresses with transfer hooks.

Support

FAQs

Can't find an answer? Chat with us on Discord, Twitter or Linkedin.