Submitted by ladboy233, also found by adriro, immeas, bin2chen, and said
https://github.com/code-423n4/2023-12-particle/blob/a3af40839b24aa13f5764d4f84933dbfa8bc8134/contracts/libraries/LiquidityPosition.sol#L195 
https://github.com/code-423n4/2023-12-particle/blob/a3af40839b24aa13f5764d4f84933dbfa8bc8134/contracts/libraries/LiquidityPosition.sol#L258
When user mint NFT add liquidity, user can specify two parameter, params.amount0Min and params.amount1Min
If the minted amount is too small, transaction revert in this check in Uniswap position manager when addling liquidity.
However, when addling liquidity, the parameter amount0Min and amount1Min is set to 0.
As Uniswap V3 docs highlight:
https://docs.uniswap.org/contracts/v3/guides/providing-liquidity/mint-a-position#calling-mint
If the user transaction suffers from frontrunning, a much less amount of token can be minted.
Same issue happens when user decrease liquidity:
The amount0 and amount1Min are set to 0.
When MEV bot frontruns the decrease liquidity, much less amount0 and amount1 are released.
Recommend do not hardcode slippage protection parameter amount0Min and amount1Min to 0 when increase liquidity or decrease liquidity.
0xleastwood (Judge) commented:
wukong-particle (Particle) confirmed and commented:
For this audit, 5 reports were submitted by wardens detailing low risk and non-critical issues. The report highlighted below by immeas received the top score from the judge.
The following wardens also submitted reports: adriro, bin2chen, ladboy233, and said.
