ENS Developer: Null character vulnerability in ENS subgraph has been resolved and will be tested as necessary

ENS developer Nick Johnson issued a document stating that the problem of null character vulnerabilities in ENS subgraphs that appeared twice has been resolved and preventive measures have been taken. Since The Graph's PostgreSQL does not store null characters in text columns, an attacker could exploit this vulnerability to impersonate any domain name already registered by another user when adding null byte characters before and after domain name creation. The bug was first discovered last April, and ENSLabs' solution was to simply double-check that the query's label hash matches the one provided by the subgraph. But the vulnerability resurfaced last December, and ENSLabs will reapply the same patch that is compatible with the current feature set in the metadata service, and will carry out the necessary tests and descriptions, as well as comments alongside the code. Also, each tag is manually checked for null characters, and a unit test is added to prevent regressions. The preventative measure proposed by Nick Johnson is to deploy the metadata service semi-automatically. All the code merged into the main branch will start the -no-traffic deployment, and then distinguish the traffic.