A security researcher has reported a serious vulnerability in BIND 9, the software widely used in the Internet’s DNS addressing system.
Users of the software, which include ISPs and large companies, are being advised to patch the software immediately to prevent end users from being vulnerable to pharming attacks, when they are directed to a Web site set up by criminals.
BIND 9, or Berkeley Internet Name Domain 9, is among the most widely used software packages used on DNS (Domain Name System) servers. When a user types a Web address into a browser, the request goes to a DNS server, which finds the corresponding numerical IP (Internet protocol) address and locates the Web site.
For security purposes, when a browser queries a DNS server, a random 16-bit transaction ID is used to verify the response from the server. However, according to Amit Klein, chief technology officer at security vendor Trusteer Ltd., the transaction ID is not random at all.
“On the contrary, this transaction ID is very predictable,” he wrote in a paper describing the problem. The vulnerability in BIND 9 could allow an attacker to force the DNS server to return an incorrect Web site to a user, a trick known as DNS cache poisoning, or pharming. The problem exists in all BIND 9 releases when the software is being used in a caching server configuration, Klein wrote.
Other security watchers confirmed the problem. “This is very much a feasible attack,” wrote Johannes Ullrich, chief technical officer of the SANS Internet Storm Center. “Best to patch your BIND server soon.”
Klein released his paper the same day that Internet Systems Consortium Inc. issued a patch for the problem. ISC is a nonprofit company and the caretaker of BIND 9, which is used on some 80 per cent of the DNS servers on the Internet. ISC advised users to install an upgrade for BIND 9 from its Web site.
The problem is particularly worrisome since desktop security software is not effective at preventing this style of attack, Klein wrote. The attack does not directly involve a user’s computer or the DNS server, but rather data that is cached on the server.
Most DNS servers cache queries, or store them in memory, to improve performance. But if an attacker requests a Web address that is not stored in the server’s cache, a hacker could flood the cache with false information, such as the address of a different Web site, which would then be returned for future DNS queries, Klein wrote.