Permissions - notSameBlock
is insufficient for reentrancy protection
#341
Labels
2 (Med Risk)
Assets not at direct risk, but function/availability of the protocol could be impacted or leak value
bug
Something isn't working
duplicate
This issue or pull request already exists
invalid
This doesn't seem right
Handle
ScopeLift
Vulnerability details
Impact
TBD how bad the impact is
The docs mention that the
notSameBlock
modifier (and associated_notSameBlock()
method) is used to guard against reentrancy. However, users can still call a method twice in a single transaction by using transferring assets/positions between two accounts they control, and re-entering with the other accountProof of Concept
N/A
Tools Used
Recommended Mitigation Steps
Change
notSameBlock
to a standard reentrancy guard such as this one from SolmateThe text was updated successfully, but these errors were encountered: