- 10 Hot Big Data Startups to Watch
- 11 Unique Uses for Google Glass, Demonstrated by Celebs
- How to Export Your Google Reader Account
- How to Better Engage Millennials (and Why They Aren't Really so Different)
That's what happened Friday, when Dan Kaminsky, the security researcher who uncovered a critical flaw in the Doman Name System (DNS) software used to direct traffic on the Internet, gave a synopsis of the problem and what has been done to fix it.
Computerworld readers, of course, have known about the threat since July 8, when Kaminsky announced the vulnerability and talked about the multi-vendor patch effort he helped coordinate.
However, the threat escalated last week after other researchers guessed some of the bug's technical details, and then increased even more days later when attack code went public.
Are you at risk? If so, what do you do about it? We'll tackle those questions and a few others.
What's all the fuss? A basic flaw in the Domain Name System makes it much easier than originally thought to insert bogus information into the Internet's routing infrastructure.
Successful "cache poisoning" attacks let hackers reroute users' requests to, say, yourbestbanksite.com, to one that looks like Your Best Bank, but is in fact a fake created to dupe people into entering confidential information, such as their online banking usernames and passwords. All of this happens silently and behind the scenes, so no one's the wiser.
Here's how Kaminsky put it: "A bad guy has a 1-in-65,000 chance of stealing your Internet connection, and he can try a couple thousand times a second."
By the way, this explanation by Kaminsky is among the few around we think is understandable to the DNS layman. Recommended reading.
Patches are out, right? So what's the problem? Yes, some vendors issued patches on July 8 as part of a coordinated release. But not all DNS servers have been fixed.
Far from it, in fact, according to the available numbers.
Kaminsky, who tracks the results users get when they run the testing tool on at his blog (see "How do I know if I'm vulnerable," next section) said Saturday that at least 52% of DNS servers had not been patched. That number, however, is down from the 85% vulnerable in the first days after those patches were released.
Austrian security researchers issued a paper Thursday ( download PDF ) that claimed more than two-thirds of that country's DNS servers remained unpatched, a situation they called "rather grim."
How do I know if I'm vulnerable? Several free online tools will tell you whether the DNS resolving server you use has been patched.
Kaminsky's blog has one. Click "Check My DNS" at the upper right under the "DNS Checker" heading.
DNS-OARC has a Web-based testing tool as well instructions on using the Unix "dig" command.
DNSstuff.com also boasts a Web testing tool. Click "Test Now" in the box at the lower left of the home page; the box is tagged as "DNS Vulnerability Check."
What do I do if I'm vulnerable? Patches are out, but as Kaminsky has said, this is really a problem for ISP (Internet Service Providers) and companies -- which maintain DNS servers -- to fix, rather than an end-user issue.