Submitted by 0xDetermination, also found by SBSecurity, maanas (1, 2), al88nsk, PwnStars, Pessimistic, dethera, ThreeSigma, 0xblackskull, xAriextz, blutorque, neumo, tsvetanovv, sces60107, pina, oakcobalt, Breeje, ADM, tapir, said, debo, 0xweb3boy, and Satyam_Sharma
https://github.com/code-423n4/2023-09-venus/blob/main/contracts/Tokens/Prime/Prime.sol#L200-L230 
https://github.com/code-423n4/2023-09-venus/blob/main/tests/hardhat/Prime/Prime.ts#L294-L301
updateScores() is meant to be called to update the scores of many users after reward alpha is changed or reward multipliers are changed. An attacker can cause calls to Prime.updateScores() to out-of-gas revert, delaying score updates. Rewards will be distributed incorrectly until scores are properly updated.
updateScores() will run out of gas and revert if any of the users passed in the argument array have already been updated. This is due to the continue statement and the incrementing location of i:
An attacker can frontrun calls to updateScores() with a call to updateScores(), passing in a 1-member array of one of the addresses in the frontran calls argument array. The frontran call will run out of gas and revert, and only one of the users intended to be updated will actually be updated.
Paste and run the below test in the mint and burn scenario in Prime.ts (line 302)
Hardhat
Increment i such that continue doesnt result in infinite looping:
0xRobocop (Lookout) commented:
chechu (Venus) confirmed, but disagreed with severity and commented:
0xDjango (Judge) commented:
chechu (Venus) commented:
