Lack of path validation
The swap functions swapExactTokensForTokens of _swapUnderlyingToAsset accepts routes parameter with arbitrary consequences of routes, consisting of (tokenIn, tokenOut, stable, factory) parameters. Neither Adapter or Router performs a check that the tokenOut parameter of the previous route matches the tokenIn parameter of the successive route.
This may cause unexpected bahaviour
Manual Review
recommend improving the validation of the routes parameter
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.