-
Notifications
You must be signed in to change notification settings - Fork 982
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect detector results to investigate #2214
Comments
For 2, there isn't a state variable written after the call that's read before the call or in other functions |
But I can reenter the function or any other function (cross-function reentrancy). So Slither doesn't care about this general reentrancy? |
What is the exploit? Here, it seems benign to call the functions reentrantly as it'd have the same affect as calling it twice, right? I'm not sure one would do except add nonreetrant modifiers on any function that makes an external call. |
There is no exploit for this case, I was just wondering whether this could lead to false negatives. Does Slither detect cross-function reentrancies? |
Right, what about 1) above? Why is this not discovered? |
From @pcaversaccio
1
2
The text was updated successfully, but these errors were encountered: