DNS Flaw Is A Serious Security Threat
from the patch-those-servers dept
Aaron Massey has a good write-up of the DNS vulnerability that was discovered by security researcher Dan Kaminsky and leaked onto the Internet this week. In a nutshell, a flaw in the design of the DNS protocol (which translates domain names like "techdirt.com" to IP addresses) will make it possible for malicious individuals to invisibly redirect web traffic from legitimate sites to sites of the attacker's choosing. This is a huge deal because a ton of online applications and services depend on reliable DNS for their security. You might think you're visiting your bank's website, but if your DNS server isn't patched you could really be sending your password to hackers in Russia. Kaminsky tells Wired that fewer than half of the DNS servers on the Internet were patched when the details of the vulnerability leaked, so it's a real problem. If your ISP hasn't patched its DNS servers, you can protect yourself by switching to OpenDNS until they do so.
There's a long-running argument in computer security circles about the best way to release information about security vulnerabilities, with a lot of security professionals favoring immediate, public disclosure of all vulnerabilities. Kaminsky chose not to go the public disclosure route because he felt this bug was too serious to take the risk of its being misused. Kaminsky approached the major DNS vendors in March, and managed to keep the details secret long enough for them to develop fixes for their products. Then, on July 8, Kaminsky announced the simultaneous release of these fixes, while still keeping the details of the vulnerability secret. (The fixes worked in a general enough way that they didn't give away the details of the vulnerability.) He had been intending to keep it secret until August 8, so that systems administrators would have a full month to prepare their networks. Unfortunately, the information leaked out on Monday, leading to a scramble to patch the remaining DNS servers before exploits start showing up. Given the scope of the patching effort (16 people from various organizations were invited to the secret March summit among DNS vendors), I think it's pretty impressive that the details didn't leak out earlier.
Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Filed Under: disclosure, dns flaw, security
Reader Comments
Subscribe: RSS
View by: Time | Thread
OpenDNS?
[ link to this | view in chronology ]
Re: OpenDNS?
http://www.doxpara.com/
You can switch to OpenDNS and then use his [check my dns] button.
[ link to this | view in chronology ]
yes, but ssl certificates should still offer some protection
[ link to this | view in chronology ]
DNS still insecure
[ link to this | view in chronology ]
Re: DNS still insecure
[ link to this | view in chronology ]
And Exploits Start Showing Up
[ link to this | view in chronology ]
Re: Main Article
I just read this article this morning over at wired:
http://www.wired.com/politics/security/commentary/securitymatters/2008/07/securitymatters_07 23
It is another post by one of the more favored security gurus, Bruce Schneier.
The basic points of the articles you guys have about the attack are similar. Bruce almost makes a couple of good points that I feel are worth mentioning here. As you guys have had a few articles in the past noting, shooting the messanger is a BAD IDEA. People should not be saying anything bad about Kaminsky or harboring him any ill will. He did go about it in a very good manner trying to help people for the good of the cause. I recall at least a few articles (although not the specifics) on Techdirt about people trying to sue those who were trying to help. I am sure that at least one of them had to do with those little secure cards that the company wanted the US to use for national id cards. There was a flaw pointed out in them, and the company threatened to sue the guy if he released the details. With regards to shooting the messanger, I must say that I have not seen anyone make bad comments about Kaminsky yet, but I do not doubt somebody has in their misdirected rage. This is a topic that Bruce mentions in the article, and Techdirt has as well in the past.
Another topic Techdirt has covered many times, that Bruce mentions in his article, is that these systems are naturally insecure. They would be far better if they were designed from the ground up with security in mind. Include security experts from the start of design so that security is innately part of the system. As Bruce so adequetly puts it, "Stop assuming that systems are secure unless demonstrated insecure; start assuming that systems are insecure unless designed securely." He even mentions voting machines and ID cards right before that. And I know you guys have covered them before many times.
[ link to this | view in chronology ]
OpenDNS
http://blog.opendns.com/2008/07/08/opendns-keeping-you-safe/
[ link to this | view in chronology ]
[ link to this | view in chronology ]
[ link to this | view in chronology ]
[ link to this | view in chronology ]
[ link to this | view in chronology ]