Malicious takeover of previously owned ENS names #7953
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ensbot
requested review from
danjm,
frankiebee,
Gudahtt and
whymarrh
as code owners
|
Thanks but no thanks @ensbot, we'll fix this with a different commit. |
|
See also #7954 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Impact
A user who owns an ENS domain can set a "trapdoor", allowing them to transfer ownership to another user, and later regain ownership without the new owner's consent or awareness.
Patches
A new ENS deployment is being rolled out that fixes this vulnerability in the ENS registry. The registry is newly deployed at 0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e.
Workarounds
Do not accept transfers of ENS domains from other users on the old registrar.
Check the migration guide in our docs.