Submitted by izhuer
Specifically, according to the documentation, there will be a deprecation period that two types of .eth registrar controllers are active.
The current .eth registrar controller can directly register ETH2LD and send to the user, while the new one will automatically wrap the registered ETH2LD.
If the two .eth registrar controllers are both active, an ETH2LD node can be implicitly unwrapped while the NameWrapper owner remains to be the hacker.
Note that this hack can easily bypass the patch of [H-01].
Considering the following situtation.
For example,
Note that it does not mean the impact of the above hack is limited in the deprecation period.
What the hacker needs to do is to re-registers sub1.eth via the old .eth registrar controller (in the deprecation period). He can then launch the attack any time he wants.
May need to discuss with ENS team. A naive patch is to check whther a given ETH2LD node is indeed wrapped every time we operate it. However, it is not gas-friendly.
jefflau (ENS) confirmed
Alex the Entreprenerd (judge) commented:
izhuer (warden) commented:
csanuragjain (warden) commented:
