Submitted by oakcobalt
/contracts/pool-manager/src/helpers.rs#L426
/contracts/pool-manager/src/helpers.rs#L429
Current slippage calculation for providing liquidity to stableswap pool uses simple sum of unscaled asset balance. This is vulnerable because it doesnt account for differences in asset decimals, which might cause slippage calculation to be invalid.
Vulnerable case: (1000000 usdc + 1e18 dai) vs (1e18 usdc + 1e6 dai)
The pool impact of depositing 1000000 usdc + 1e18 dai vs depositing 1e18 usdc + 1e6 dai are expected to diverge.
However, in the current slippage check, both cases will lead to the same deposits_total. This invalidates the pool_ratio/deposit_ratio calculation. 
/contracts/pool-manager/src/helpers.rs#L424-L429
Flows: contracts/pool-manager/src/liquidity/commands::provide_liquidity  helpers::assert_slippage_tolerance
As we can see, in the vulnerable case above, pools_total and deposits_total will be the same in both cases where the actual deposits assets amount when aligned to 18 decimals and the actual deposit assets value vastly differ. This invalidates the comparison check results. 
Scale the asset to the same decimal before performing sum.
jvr0x (MANTRA) confirmed via chat with C4 staff
For this audit, 11 reports were submitted by wardens detailing low risk and non-critical issues. The report highlighted below by Bauchibred received the top score from the judge.
The following wardens also submitted reports: 0xcb90f054, axelot, Daniel526, jasonxiale, Lambda, oakcobalt, OxElliot, Rhaydden, Sparrow, and Tigerfrake.
