SHARE
Follow this article on Twitter Facebook LinkedIn Bookmark and Share
Home >> Security >> Hacking and Viruses

1.3 million DNS servers still vulnerable to cache-poisoning

1.3 million DNS servers still vulnerable to cache-poisoning

By:  Bryan Betts  On: 10 Nov 2008 For: IDG News Service (London Bureau)(NA) Creator

At least one in 10 servers is still susceptible to domain name systems attack despite fixes being made available more than four months ago

More than 10 percent of the Internet's DNS (Domain Name System) servers are still vulnerable to cache-poisoning attacks, according to a worldwide survey of public-facing Internet nameservers.

That's despite it being several months since the vulnerabilities were disclosed and fixes made available, said DNS expert Cricket Liu, whose company, Infoblox , the annual survey.

"We estimate there's 11.9 million nameservers out there, and over 40 percent allow open recursion, so they accept queries from anyone. Of those, a quarter are not patched. So there's 1.3 million nameservers that are trivially vulnerable," said Liu, who is Infoblox's vice president of architecture.

Other DNS servers may well allow recursion, but are not open to everyone, so they were not picked up by the survey, he said.

More information on dealign with flaws and patches

Liu said the cache-poisoning vulnerability, which is often named after Dan Kaminsky, the security researcher who published details of it in July, is genuine: "Kaminsky was exploited within days of being made public," he said.

Modules targeting the vulnerability have been added to the hacking and penetration testing tool Metasploit , for instance. Ironically, one of the first DNS servers compromised by a cache poisoning attack was one used by Metasploit's author, HD Moore.

For now, the antidote to the cache-poisoning flaw is port randomization. By sending DNS queries from varying source ports, this makes it harder for an attacker to guess which port to send poisoned data to.

However, this is only a partial fix, Liu warned. "Port randomization mitigates the problem but it doesn't make an attack impossible," he said. "It is really just a stopgap on the way to cryptographic checking, which is what the DNSSEC security extensions do.

"DNSSEC is going to take a whole lot longer to implement though, as there's a lot of infrastructure involved -- key management, zone signing, public key signing, and so on. We thought we might see a noticeable uptake in DNSSEC adoption this year, but we saw only 45 DNSSEC records out of a million sample. Last year we saw 44."


Sign up for our Newsletters
Tags: DNS servers












Print |  Views: 1121   |   Rating:offoffoffoffoff  (0 votes)
Rate this article on a scale of
1 to 5 stars,5 being the best.




Bryan Betts Bryan Betts is a contributor to the International Data Group (IDG) News Service, which publishes global technology stories from bureaus around the world to more than 300 publications in more than 60 countries.

Related Content

Budget constraints might hamper DNS security
Budget constraints might hamper DNS security With the year coming to a close, DNS experts worry that security projects aimed at fixing critical flaws with take a backseat to cost-cutting measures
What to do in response to the DNS bombshell
What to do in response to the DNS bombshellA Canadian analyst advises e-businesses to ‘hound’ their ISPs asking for proof they have taken safeguards against DNS vulnerabilities. What Dan Kaminsky told Black Hat attendees
Greetings from your hijacker
Greetings from your hijackerA new round of greeting card spam that draws users to attack sites relies on a sophisticated multi-pronged, multi-exploit strike force to infect machines.
CanSecWest PWN to OWN 2008
so this is a rather interesting story, which beautifully lends itself to sensational press and great article titles like “macbook air hacked in two minutes” and “vista falls, linux holds strong”. this frankly, is exactly why tippingpoint and cansec
blog comments powered by Disqus