Open code423n4 opened 2 years ago
Potential reentrance in claimRewards Dup of #86 (Med)
Potential out of gas in massUpdatePools Doesn't actually solve as you can still run out of gas in an external call, and, for other sponsor mistakes the function is unused
Left dust CRV & CVX in ConvexStakingWrapper Valid
should use safeTransfer Agree
Lacking event Non-critical
Adding #83 to this, the warden has shown how dust amounts can accrue over time to the vault
3+
Bumped to 4 to be 2nd best submission
@CloudEllie please create new issue for the Med finding above.
Created separate issue for "Potential reentrance in claimRewards
" - see #269
Handle
wuwe1
Vulnerability details
Potential reentrance in claimRewards
POC
https://github.com/code-423n4/2022-02-concur/blob/main/contracts/ConcurRewardPool.sol#L37-L38
Considering there are
exterTokens
, it is possible that some token will provide reentry opportunities.Mitigation
change to order of L37 and L38
Potential out of gas in massUpdatePools
POC
https://github.com/code-423n4/2022-02-concur/blob/main/contracts/MasterChef.sol#L127-L132
Mitigation
change to
Left dust CRV & CVX in ConvexStakingWrapper
POC
https://github.com/code-423n4/2022-02-concur/blob/main/contracts/ConvexStakingWrapper.sol#L179-L180
Current implementation will always left 1 CRV or CVX in the contract.
Mitigation
should use safeTransfer
These two call are not using safeTransfer
https://github.com/code-423n4/2022-02-concur/blob/main/contracts/ConvexStakingWrapper.sol#L179
https://github.com/code-423n4/2022-02-concur/blob/main/contracts/ConvexStakingWrapper.sol#L182
Lacking event
https://github.com/code-423n4/2022-02-concur/blob/main/contracts/MasterChef.sol#L86-L101
add
has no event, so it is difficult to track off-chain changes in thepoolInfo
.consider add a event like
https://github.com/sushiswap/sushiswap/blob/canary/contracts/MasterChefV2.sol#L123