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

transferOwnership should be two step process #49

Open
code423n4 opened this issue Sep 8, 2021 · 1 comment
Open

transferOwnership should be two step process #49

code423n4 opened this issue Sep 8, 2021 · 1 comment
Labels
1 (Low Risk) bug Something isn't working duplicate This issue or pull request already exists

Comments

@code423n4
Copy link
Contributor

Handle

JMukesh

Vulnerability details

Impact

Lack of two-step procedure for critical operations leaves them error-prone
if the address is incorrect, the new address will take on the functionality of the new role immediately

for Ex : -Alice deploys a new version of the whitehack group address. When she invokes the whitehack group address setter to replace the address, she accidentally enters the wrong address. The new address now has access to the role immediately and is too late to revert

https://raw.githubusercontent.com/trailofbits/publications/master/reviews/hermez.pdf

Proof of Concept

https://github.com/code-423n4/2021-08-notional/blob/4b51b0de2b448e4d36809781c097c7bc373312e9/contracts/external/actions/GovernanceAction.sol#L26

Tools Used

manual reveiw

Recommended Mitigation Steps

use a two-step procedure for all non-recoverable critical operations to prevent
irrecoverable mistakes.

@code423n4 code423n4 added 1 (Low Risk) bug Something isn't working labels Sep 8, 2021
code423n4 added a commit that referenced this issue Sep 8, 2021
@jeffywu jeffywu added the duplicate This issue or pull request already exists label Sep 11, 2021
@jeffywu
Copy link
Collaborator

jeffywu commented Sep 11, 2021

Duplicate #94

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 (Low Risk) bug Something isn't working duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants