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

Unable to remove operator at index 0 #142

Closed
code423n4 opened this issue Nov 17, 2021 · 2 comments
Closed

Unable to remove operator at index 0 #142

code423n4 opened this issue Nov 17, 2021 · 2 comments
Labels
1 (Low Risk) Assets are not at risk. State handling, function incorrect as to spec, issues with comments bug Something isn't working duplicate This issue or pull request already exists

Comments

@code423n4
Copy link
Contributor

Handle

gzeon

Vulnerability details

Impact

Unable to remove operator at index 0

Proof of Concept

https://github.com/code-423n4/2021-11-nested/blob/f646002b692ca5fa3631acfff87dda897541cf41/contracts/NestedFactory.sol#L84
revert when i == 0

Recommended Mitigation Steps

Remove the require statement as if not found it would revert due to OOB in L81;
or rewrite as follow to yield proper revert

    function removeOperator(bytes32 operator) external override onlyOwner {
        uint256 i = 0;
        uint256 len = operators.length; // Gas optimization
        while (operators[i] != operator && i < len) {
            i++;
        }
        require(i < len, "NestedFactory::removeOperator: Cant remove non-existent operator");
        delete operators[i];
    }
@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 Nov 17, 2021
code423n4 added a commit that referenced this issue Nov 17, 2021
@maximebrugel maximebrugel added the duplicate This issue or pull request already exists label Nov 17, 2021
@maximebrugel
Copy link
Collaborator

Duplicated : #58

@alcueca
Copy link
Collaborator

alcueca commented Dec 3, 2021

Using #220 instead

@CloudEllie CloudEllie added 1 (Low Risk) Assets are not at risk. State handling, function incorrect as to spec, issues with comments and removed 2 (Med Risk) Assets not at direct risk, but function/availability of the protocol could be impacted or leak value labels Dec 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 (Low Risk) Assets are not at risk. State handling, function incorrect as to spec, issues with comments bug Something isn't working duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

4 participants