Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

executeLimitOrder() calls modifyLongOi() and modifyShortOi() with wrong position size #431

Closed
code423n4 opened this issue Dec 16, 2022 · 2 comments
Labels
2 (Med Risk) Assets not at direct risk, but function/availability of the protocol could be impacted or leak value bug Something isn't working duplicate-576 satisfactory satisfies C4 submission criteria; eligible for awards

Comments

@code423n4
Copy link
Contributor

Lines of code

https://github.com/code-423n4/2022-12-tigris/blob/588c84b7bb354d20cbca6034544c4faa46e6a80e/contracts/Trading.sol#L513-L517

Vulnerability details

Impact

executeLimitOrder() calls modifyLongOi() and modifyShortOi() with wrong position size, causes the following state variables wrongly updated

// Position.sol
fundingDeltaPerSec
longOi
shortOi

// PairsContract.sol
_idToOi

Proof of Concept

The vulnerability points

function executeLimitOrder(
    uint _id, 
    PriceData calldata _priceData,
    bytes calldata _signature
) 
    external
{
    unchecked {
        //...
        if (trade.direction) {
            tradingExtension.modifyLongOi(trade.asset, trade.tigAsset, true,
                trade.margin*trade.leverage/1e18); // @audit should be (trade.margin - _fee)*trade.leverage/1e18
        } else {
            tradingExtension.modifyShortOi(trade.asset, trade.tigAsset, true,
                trade.margin*trade.leverage/1e18); // @audit should be (trade.margin - _fee)*trade.leverage/1e18
        }
        // ...
    }
}

Tools Used

VS Code

Recommended Mitigation Steps

Use margin after fee to calculate position.

@code423n4 code423n4 added 2 (Med Risk) Assets not at direct risk, but function/availability of the protocol could be impacted or leak value bug Something isn't working labels Dec 16, 2022
code423n4 added a commit that referenced this issue Dec 16, 2022
@c4-judge
Copy link
Contributor

GalloDaSballo marked the issue as duplicate of #576

@c4-judge
Copy link
Contributor

GalloDaSballo marked the issue as satisfactory

@c4-judge c4-judge added the satisfactory satisfies C4 submission criteria; eligible for awards label Jan 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2 (Med Risk) Assets not at direct risk, but function/availability of the protocol could be impacted or leak value bug Something isn't working duplicate-576 satisfactory satisfies C4 submission criteria; eligible for awards
Projects
None yet
Development

No branches or pull requests

2 participants