FAQ: The DNS bug and you
Attack code hit the street last week, so what's your move?
Computerworld - You know a bug is big news when it makes National Public Radio's All Things Considered, the network's afternoon drive-time show.
That's what happened on Friday, when Dan Kaminsky, the security researcher who uncovered a critical flaw in the Domain 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 multivendor patch effort he helped coordinate.
However, the threat escalated last week after other researchers guessed some of the bug's technical details, and it then increased even more a few 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.
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.
- Deep Security +VMware vSphere with Operations Management Most midsize organizations are highly virtualized on VMware, and while this has produced significant savings, it also has created new challenges when it...
- 3 Questions to Ask Your DNS Host about Lowering DDoS Risks Neustar has had wide-ranging conversations with clients wanting to know how they can optimize protection as DDoS attacks increase in frequency and size.
- The Danger Deepens: 2014 Neustar Annual DDoS Attacks and Impact Report This report compares DDoS findings from 2013 to 2012, based on a survey of 440 North American companies, including 139 businesses delivering technology...
- DDoS Infographic: How Are Attacks Evolving? For the third consecutive year, Neustar surveyed businesses across major industries to track the evolution of DDoS attacks. Are they more frequent? Larger?...
- How to Use Crowd-Sourced Threat Intelligence to Stop Malware in its Tracks Threat sharing networks have been around for a long time, however they have typically been "invitation-only", available to only large companies, or those...
- An Incident Response Playbook: From Monitoring to Operations As cyber-attacks grow more sophisticated, many organizations are investing more into incident detection and response capabilities. In this webcast, learn how to develop... All Malware and Vulnerabilities White Papers | Webcasts