Submitted by 0xjuicer, also found by csanuragjain
Rewards distribution can be delayed/never distributed on AuraLocker.sol#L848 
Someone malicious can delay the rewards distribution for non cvxCrv tokens distributed on AuraLocker.sol.
1: Attacker will send one wei of token that are distributed on the AuraLocker.sol  to AuraStakingProxy.
2: Attacker will call distributeOther.
The function will call notifyRewardAmount that calls _notifyReward
When calling _notifyReward the rewards left to distribute over the 7 days are redistributed throughout a new period starting immediately.
Example: If the reward rate is 1 token (10**18) per second and 3.5 days are left (302400 seconds), we get a leftover of 302400 tokens. this is then divided by 604800, the reward rate is now 0.5 and the user of the protocol will have to wait one week for tokens that were supposed to be distributed over 3.5 days. This can be repeated again and again so that some rewards are never distributed.
I can see that queueNewRewards has some protective mechanism. A new period is started only if the token that is added on top of the already distributed tokens during the duration is over 120%.
I suggest adding a similar check to queueNewRewards
0xMaharishi (Aura Finance) confirmed, but disagreed with severity
0xMaharishi (Aura Finance) resolved:
