issues
search
code-423n4
/
2024-05-munchables-validation
0
stars
0
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Approval After Disapproval in `approveUSDPrice` Function
#579
c4-bot-8
opened
6 months ago
0
`lockedToken.reminder` of a Previous Lock Resets to 0 If User/Attacker Locks Funds Between Two Lockdrop Events
#578
c4-bot-7
opened
6 months ago
0
Subsequent token locks extend the `unlockTime` for all previously locked tokens.
#577
c4-bot-6
opened
6 months ago
0
QA Report
#576
c4-bot-8
opened
6 months ago
0
Lack of Quantity Check in lock and lockOnBehalf Functions.
#575
c4-bot-6
opened
6 months ago
0
Unauthorized Increase in Schnibbles via Zero-Quantity Unlock calls.
#574
c4-bot-8
opened
6 months ago
0
Lack of _quantity Check in lock and lockOnBehalf Functions.
#573
c4-bot-8
opened
6 months ago
0
Rebasing token USDB is not being handled properly
#572
c4-bot-8
opened
6 months ago
0
Unlock Time Can Be Set to a Lower Value Than the Current Unlock Time
#571
c4-bot-8
opened
6 months ago
0
LockManager does not handle Fee on Transfer tokens properly
#570
c4-bot-6
opened
6 months ago
0
Disapproving voters may be forced to approve USD price updates
#569
c4-bot-8
opened
6 months ago
0
QA Report
#568
c4-bot-2
opened
6 months ago
0
Player can set a very small lockup time of 1 second depending on a frontrunning condition
#567
c4-bot-2
opened
6 months ago
0
`unlockTime` gets set incorrectly in `setLockDuration`
#566
c4-bot-3
opened
6 months ago
0
Locking tokens subsequent times by users increases lock duration for previous locks also
#565
c4-bot-2
opened
6 months ago
0
Incompatibility with Rebased Tokens Leads to Balance Discrepancies
#564
c4-bot-3
opened
6 months ago
0
`lockedToken.remainder` can get corrupted depending on when `lock()` is called
#563
c4-bot-7
opened
6 months ago
0
Spamming wrong price could disrupt protocol stability
#562
c4-bot-9
opened
6 months ago
0
Attacker can call `onBehalfOf` with 1 wei to extend lock period and prevent innocent user from unlocking
#561
c4-bot-9
opened
6 months ago
0
Once a player deposits an amount of a certain token, he/she cannot deposit a further quantity of the same token without resetting the lockDuration on the whole deposited amount
#560
c4-bot-9
opened
6 months ago
0
flaw Due to Uninitialized Loop in getLockedWeightedValue
#559
c4-bot-9
opened
6 months ago
0
PriceFeed role can disapprove and able to approve same proposal
#558
c4-bot-7
opened
6 months ago
0
funds can be unlocked before unlock time !
#557
c4-bot-7
opened
6 months ago
0
Schnibbles earned are lost if the token is deactivated
#556
c4-bot-4
opened
6 months ago
0
Incorrect state change in `_lock` function allows user to steal tokens.
#555
c4-bot-4
opened
6 months ago
0
Missing logic to adjust `lockedToken.remainder` during `unlock` permits acquiring subsequent NFT without locking the required amount.
#554
c4-bot-10
opened
6 months ago
0
InvalidLockDurationError revert can cause a block for users when use lock method
#553
c4-bot-10
opened
6 months ago
0
Lack of Validation for `_price` Parameter in `proposeUSDPrice` Function
#552
c4-bot-10
opened
6 months ago
0
The lock() function will always revert if minLockDuration is bigger than the MaxLockDuration
#551
c4-bot-1
opened
6 months ago
0
QA Report
#550
c4-bot-4
opened
6 months ago
0
configuredTokenContracts array has no where to delete or remove
#549
c4-bot-4
opened
6 months ago
0
Users can gain rewards with zero quantity
#548
c4-bot-10
opened
6 months ago
2
Fail Handling Players with No Locked Tokens
#547
c4-bot-3
opened
6 months ago
0
Anyone can grief users unlock time by locking dust amounts on behalf of that user .
#546
c4-bot-4
opened
6 months ago
0
USD price proposer can double vote for the USD price he proposed.
#545
c4-bot-3
opened
6 months ago
0
Users can gain rewards from unlock method more than it should be
#544
c4-bot-3
opened
6 months ago
0
No check in disapproveUSDPrice() to make sure proposal with equal number of votes does not get deleted
#543
c4-bot-9
opened
6 months ago
0
unlock with partial quantity can cause user loss of rewards.
#542
c4-bot-1
opened
6 months ago
2
unlock with partial quantity can cause user loss of rewards.
#541
c4-bot-5
opened
6 months ago
0
QA Report
#540
c4-bot-10
opened
6 months ago
0
Updating multiple contract's USD price can lead to compromising the USD price for some contracts.
#539
c4-bot-4
opened
6 months ago
0
unlock function also uses notpaused modifier thus it can prevent the user to withdraw their tokens.
#538
c4-bot-5
opened
6 months ago
0
If `configuredTokenContracts` will become large it will lead to DoS of some function.
#537
c4-bot-7
opened
6 months ago
0
configuredTokenContracts can be blocked from updating unlockTime in setLockDuration
#536
c4-bot-10
opened
6 months ago
0
Dubious typecast in the functions called setLockDuration & _lock proposeUSDPrice & configureLockDrop and unlock function
#535
c4-bot-3
opened
6 months ago
0
Users cannot withdraw their locked tokens if the contract is paused
#534
c4-bot-10
opened
6 months ago
0
`lockRecipient` and `onBehalfOf` address could be same.
#533
c4-bot-5
opened
6 months ago
0
QA Report
#532
c4-bot-6
opened
6 months ago
0
QA Report
#531
c4-bot-6
opened
6 months ago
2
value of lockedToken.remainder is not reduced to zero even when the user has withdrawn all the tokens he locked.
#530
c4-bot-6
opened
6 months ago
0
Previous
Next