{"id":100585,"date":"2021-06-23T10:22:42","date_gmt":"2021-06-23T08:22:42","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/oshibka-v-bind-9-16-17-privodyashhaya-k-nevernoj-obrabotke-simvola-w-v-dns-zaprosah"},"modified":"2021-06-23T10:22:42","modified_gmt":"2021-06-23T08:22:42","slug":"oshibka-v-bind-9-16-17-privodyashhaya-k-nevernoj-obrabotke-simvola-w-v-dns-zaprosah","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/oshibka-v-bind-9-16-17-privodyashhaya-k-nevernoj-obrabotke-simvola-w-v-dns-zaprosah","title":{"rendered":"A bug in BIND 9.16.17 leads to incorrect handling of the W character in DNS queries.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Corrective updates have been released for the stable branch of the BIND DNS server 9.16.18 and the experimental branch 9.17.15 currently in development, addressing a critical bug that appeared in the releases of BIND 9.16.17 and 9.17.14, published last week (the day after these releases, developers warned about the issue and recommended not to install versions 9.16.17 and 9.17.14). <\/p>\n
In versions 9.16.17 and 9.17.14, the character mapping tables for uppercase and lowercase characters (maptoupper and maptolower) missed the character \u00abw\u00bb, leading to the replacement of characters \u00abW\u00bb and \u00abw\u00bb in domain names with the sequence \u00ab\u00bb and returning incorrect results when processing mask requests. For example, if the DNS zone contained the record \u00ab*.sub.test.local. 1 A 127.0.0.1\u00bb, the request for the name UVW.sub.test.local resulted in a response that returned the name \u00abuv.sub.test.local\u00bb instead of \u00abuvw.sub.test.local\u00bb. <\/p>\n
Additionally, there were issues with replacing the character \u00abw\u00bb with \u00ab\u00bb during dynamic zone updates if the case of the character \u00abw\u00bb in the request differed from the case in the DNS zone. For instance, if there was a record \u00abWW.example\u00bb in the zone and an update was sent for \u00abfoo.ww.example.\u00bb, it was processed as \u00abfoo..example\u00bb. Issues with character replacement could also occur during zone transfer operations from the primary to the secondary DNS server. <\/p>\n
The release of update 9.16.18 was delayed due to the discovery of two additional bugs that remained unresolved in versions 9.16.18 and 9.17.15. These bugs cause mutual blocking during initialization and manifest in configurations where the same zones are used in dnssec-policy present in different views. Users with such settings are recommended to roll back to version BIND 9.16.16. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"