Skip to content
This repository has been archived by the owner on Nov 26, 2023. It is now read-only.

Nyx - No slippage control #660

Closed
sherlock-admin opened this issue May 24, 2023 · 0 comments
Closed

Nyx - No slippage control #660

sherlock-admin opened this issue May 24, 2023 · 0 comments
Labels
Duplicate A valid issue that is a duplicate of an issue with `Has Duplicates` label High A valid High severity issue Reward A payout will be made for this issue

Comments

@sherlock-admin
Copy link
Contributor

sherlock-admin commented May 24, 2023

Nyx

high

No slippage control

Summary

When swapping amountOutMinimum is set to 0. There is no slippage protection, protocol can lose funds.

Vulnerability Detail

function UniV3SwapInput(
        bytes memory _path,
        uint256 _sellAmount
    ) public override onlyBalancer {
        IV3SwapRouter.ExactInputParams memory params = IV3SwapRouter
            .ExactInputParams({
                path: _path,
                recipient: address(this),
                //deadline: block.timestamp,
                amountIn: _sellAmount,
                amountOutMinimum: 0
            });
        uniRouter.exactInput(params);
    }

When the protocol needs to rebalance pool, the protocol buys collateral or sells. And it uses UniV3SwapInput() function for it.

IUSSD(USSD).UniV3SwapInput(collateral[i].pathsell, amountToSellUnits);

But there is no slippage control in UniV3SwapInput() function. If Unexpected swaps occur, the protocol can suffer a huge loss due to no slippage protection.

Impact

Unexpected swaps can occur, and the protocol can suffer a huge loss due to no slippage protection.

Code Snippet

https://github.com/sherlock-audit/2023-05-USSD/blob/main/ussd-contracts/contracts/USSD.sol#L227-L240

Tool used

Manual Review

Recommendation

amountOutMinimum: 0

add slippage control to UniV3SwapInput() function.

Duplicate of #673

@github-actions github-actions bot closed this as completed Jun 5, 2023
@github-actions github-actions bot added High A valid High severity issue Duplicate A valid issue that is a duplicate of an issue with `Has Duplicates` label labels Jun 5, 2023
@sherlock-admin sherlock-admin added the Reward A payout will be made for this issue label Jun 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Duplicate A valid issue that is a duplicate of an issue with `Has Duplicates` label High A valid High severity issue Reward A payout will be made for this issue
Projects
None yet
Development

No branches or pull requests

1 participant