issues
search
code-423n4
/
2022-06-badger-findings
0
stars
0
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
QA Report
#58
code423n4
opened
2 years ago
1
Gas Optimizations
#57
code423n4
opened
2 years ago
1
withdrawalSafetyCheck is handled incorrectly. (Resubmit due to wrong mitigation)
#56
code423n4
closed
2 years ago
1
QA Report
#55
code423n4
opened
2 years ago
0
Gas Optimizations
#54
code423n4
opened
2 years ago
1
Gas Optimizations
#53
code423n4
opened
2 years ago
1
QA Report
#52
code423n4
opened
2 years ago
2
QA Report
#51
code423n4
closed
2 years ago
1
Missing proper policy for contract in pause mode
#50
code423n4
closed
2 years ago
1
BribesProcessor is not notified for new round of bribes
#49
code423n4
closed
2 years ago
1
Users can bypass processLocksOnReinvest
#48
code423n4
closed
2 years ago
1
Gas Optimizations
#47
code423n4
opened
2 years ago
1
QA Report
#46
code423n4
opened
2 years ago
1
QA Report
#45
code423n4
opened
2 years ago
2
Gas Optimizations
#44
code423n4
opened
2 years ago
1
Gas Optimizations
#43
code423n4
opened
2 years ago
1
QA Report
#42
code423n4
closed
2 years ago
1
Reward token (auraBal) can be locked in the strategy
#41
code423n4
closed
2 years ago
2
Sandwich attack opportunity on harvest
#40
code423n4
closed
2 years ago
2
_withdrawAll should be implemented by the other way. Currently, it is useless even in emergency case.
#39
code423n4
closed
2 years ago
1
Gas Optimizations
#38
code423n4
opened
2 years ago
0
QA Report
#37
code423n4
closed
2 years ago
1
QA Report
#36
code423n4
opened
2 years ago
1
QA Report
#35
code423n4
closed
2 years ago
1
Gas Optimizations
#34
code423n4
opened
2 years ago
2
withdrawalSafetyCheck is handled incorrectly.
#33
code423n4
closed
2 years ago
1
`_sendBadgerToTree()` Calls `BADGER.safeTransfer(to, amount)` Twice, Double Spending The Tokens
#32
code423n4
closed
2 years ago
1
with claimBribesFromHiddenHand() It's possible to send auraBAL rewards from LOCKER to bribeProcessor even so auraBAL is in protected tokens and it is supposed to get harvested in _harvest
#31
code423n4
opened
2 years ago
2
attacker can lock all the auraBAL rewards in contract address forever and they won't be accessible
#30
code423n4
closed
2 years ago
2
Gas Optimizations
#29
code423n4
opened
2 years ago
0
reentrancy by _harvest() and _deposit() code in the middle of claimBribesFromHiddenHand() external calls to tokens and change balances of AURA token so claimBribesFromHiddenHand() make wrong transfers and fund would be lost
#28
code423n4
closed
2 years ago
1
sweepRewardToken() should only be callable when contract is initialized. early AURA balance would be lost if some one call it with AURA as token and before initialization
#27
code423n4
closed
2 years ago
1
fund lose because of the direct funds transfer to vault address and cause big balance() to totalSupply() ratio and cause big division error in _mintSharesFor() (this is in previous contest scope)
#26
code423n4
closed
2 years ago
3
QA Report
#25
code423n4
opened
2 years ago
0
All withdrawal functionality is paused when contract is paused
#24
code423n4
closed
2 years ago
2
QA Report
#23
code423n4
opened
2 years ago
0
Gas Optimizations
#22
code423n4
opened
2 years ago
1
Gas Optimizations
#21
code423n4
closed
2 years ago
1
In _harvest() There is no allowed slippage defined for swap() or exitPool() so it's possible to frontrun or sandwithAttack the transaction and it creates MEV
#20
code423n4
closed
2 years ago
1
any logic that uses _sendBadgerToTree() will revert or double spend happens, because it transfers tokens then calls _processExtraToken() which tries to transfer those tokens again
#19
code423n4
closed
2 years ago
2
attacker can call sweepRewardToken() when `bribesProcessor==0` and reward funds will be lost because there is no check in sweepRewardToken() and _handleRewardTransfer() and _sendTokenToBribesProcessor()
#18
code423n4
opened
2 years ago
2
There is no check that in setBribesProcessor() the value of newBribesProcessor is not 0x0, fund will be lost or locked if by mistake value set to 0x0
#17
code423n4
closed
2 years ago
4
implementation contract for proxy pattern in MyStrategy and Vault are uninitialized and can be initialized by attacker and cause damage
#16
code423n4
closed
2 years ago
2
Update initializer modifier to prevent reentrancy during initialization
#15
code423n4
closed
2 years ago
1
QA Report
#14
code423n4
opened
2 years ago
1
QA Report
#13
code423n4
opened
2 years ago
1
Gas Optimizations
#12
code423n4
opened
2 years ago
1
Sandwitch attack over `harvest` function
#11
code423n4
closed
2 years ago
3
No slippage control when calling exitPool in _harvest function
#10
code423n4
closed
2 years ago
1
no slippage control on _harvest
#9
code423n4
closed
2 years ago
1
Previous
Next