-
Notifications
You must be signed in to change notification settings - Fork 0
Issues: sherlock-audit/2024-11-superfluid-locking-contract-judging
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
franfran20 - The Nonce Validity Check Can Lead To Lockers Losing Valid Units In A Program Pool
#82
opened Nov 24, 2024 by
sherlock-admin3
sa9933 - Anyone can create program and update user units in eppProgrammer
#81
opened Nov 24, 2024 by
sherlock-admin2
drlaravel - Timestamp Manipulation and Points Dilution in Superfluid Locking Contract
#80
opened Nov 24, 2024 by
sherlock-admin4
franfran20 - Member Units Can Be Lost Due To Overwriting Nature Of UpdateUserUnits
#78
opened Nov 24, 2024 by
sherlock-admin2
drlaravel - Precision Loss in Superfluid Locking Contract Causes Significant Token Loss for Users
#74
opened Nov 24, 2024 by
sherlock-admin4
0rpse - FluidLocker can be blocked from connecting to a pool
#72
opened Nov 24, 2024 by
sherlock-admin2
drlaravel - Flow Rate Precision Loss Vulnerability Report
#70
opened Nov 24, 2024 by
sherlock-admin3
franfran20 - Fontaine Creation Could Force Users To Only Unlock Tokens Through Instant Unlocks
#69
opened Nov 24, 2024 by
sherlock-admin2
franfran20 - A malicious user can prevent users from being able to create a locker.
#67
opened Nov 24, 2024 by
sherlock-admin3
0rpse - valid signatures can be invalidated due to how nonce validation works
#66
opened Nov 24, 2024 by
sherlock-admin2
IzuMan - Signatures can be replayed resulting in cross chain attacks
#63
opened Nov 24, 2024 by
sherlock-admin2
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.