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

Upgraded Q -> M from 143 [1663859521800] #321

Closed
code423n4 opened this issue Sep 22, 2022 · 1 comment
Closed

Upgraded Q -> M from 143 [1663859521800] #321

code423n4 opened this issue Sep 22, 2022 · 1 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 This issue or pull request already exists upgraded by judge Original issue severity upgraded from QA/Gas by judge

Comments

@code423n4
Copy link
Contributor

code423n4 commented Sep 22, 2022

Judge has assessed an item in Issue #143 as Medium risk. The relevant finding follows:

2.ETHRegistrarController.register() can pass any "resolver" and "data" parameters , then ETHRegistrarController do "functionCall "

It is possible to pass malicious parameters example :

resolver = baseRegistrar.address, and data = baseRegistrar.register()
then will register a “weird” ens

    var tx = await controller.register(
      "testtest",
      registrantAccount,
      REGISTRATION_TIME,
      secret,
      baseRegistrar.address,        //********resolver = baseRegistrar.address *******//
      [
        baseRegistrar.interface.encodeFunctionData(      //********data = baseRegistrar.register() *******//
          "register(uint256,address,uint256)",
          [
            namehash.hash("testtest.eth"),
            registrantAccount,
            REGISTRATION_TIME * 10000,
          ]
        ),
      ],
      false,
      0,
      0,
      { value: BUFFERED_REGISTRATION_COST }
    );

Recommendation add:

        require(
            resolver != address(base) &&
            resolver != address(nameWrapper) &&
            resolver != address(this)
        );

@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 upgraded by judge Original issue severity upgraded from QA/Gas by judge labels Sep 22, 2022
code423n4 added a commit that referenced this issue Sep 22, 2022
@dmvt
Copy link
Collaborator

dmvt commented Sep 22, 2022

duplicate of #132

@dmvt dmvt closed this as completed Sep 22, 2022
@dmvt dmvt added the duplicate This issue or pull request already exists label Sep 22, 2022
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 This issue or pull request already exists upgraded by judge Original issue severity upgraded from QA/Gas by judge
Projects
None yet
Development

No branches or pull requests

2 participants