Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Attacks/Breaches

Threat From DNS Bug Isn't Over, Experts Say

Further patches expected by year's end; basic flaws in critical Internet technology still unresolved

The Domain Name Server design flaw that threatened the entire Internet earlier this year has mostly been patched, but the threat is far from over, experts say.

The DNS flaw, which was discovered by IOActive researcher Dan Kaminsky in the first half of this year and resulted in the largest simultaneous security software patch in Internet history in July, was fully disclosed last month. The flaw makes it possible for attackers to exploit the recursive nature of DNS server queries to “hijack” TCP/IP sessions and potentially redirect large segments of Internet traffic to unintended destinations. (See Vendors Issue Massive Simultaneous Patch for Common Internet Flaw, Details, Exploits of Web-Wide DNS Vulnerability Revealed, and Kaminsky: DNS Vulnerability Will Affect Email, Internal Systems, Too.)

The simultaneous patch, which added a port randomization factor to the transaction ID used to authenticate Internet sessions, reduces the likelihood of session hijacking by many orders of magnitude. And most DNS servers have deployed the patch -- the number of servers vulnerable to the DNS attack has been reduced from more than 85 percent to fewer than 30 percent, Kaminsky said after conducting some vulnerability testing last week.

But the patch doesn’t fix the DNS flaw -- it only makes it more difficult for attackers to exploit it, Kaminsky and other experts are quick to say. While hackers ramp up their DNS exploits, DNS server makers and operators likely face another round of patching that will occur before the end of the year.

“We will probably see the next round of patches in the next one to three months,” Kaminsky said in an interview last week. This round probably will not be done simultaneously by all DNS server vendors, because it involves more product- and vendor-specific patching than port randomization, which could be globally applied to all DNS server environments. The next generation of patches will likely include some capability to put DNS servers into a defensive posture when they detect an onslaught of traffic attempting to exploit the flaw, he said.

And that type of traffic has already been spotted on the Internet. Paul Wood, a senior security analyst at MessageLabs, said his company has seen a 52 percent increase in traffic that appears to be seeking out recursive DNS servers that might still be vulnerable to attack. “This attack requires a large amount of traffic,” which makes it easier to spot, he said.

Attacks that exploit the design flaw have been spotted in the wild as well as on Metasploit, although most of them are designed to attack systems that have not yet been patched. Experts are concerned that the next generation of attacks will attempt to compromise the patched systems, which would be much harder but is certainly possible, they say.

“What we’ve got out there so far are truly Band-Aids,” says Alan Shimel, chief strategy officer at StillSecure, which has been monitoring the DNS flaw since it came to light. “We’re putting our finger in the dike. There are questions on how to move the solution to the firewall level. There’s no way to ensure that port randomization is being done. We need the next generation solution. We need a new DNS.”

Kaminsky agreed. Even after the next round of patches, the flaw in DNS will still be there, and the most frequently cited longer-term solution -- DNSSEC -- will require broad adoption before it can be effective, he noted. “It requires authoritative servers to opt in, and that will take time to happen.”

In the meantime, attacks will be difficult to spot, especially on unpatched DNS servers, Kaminsky observed. “It sucks to scan for it. The attacker can grab ten seconds worth of traffic and then wipe the cache. The attacker basically controls how much log data there is.”

Kaminsky says he is most concerned over the potential of an attacker to corrupt an email name server, essentially allowing him to redirect large amounts of email traffic. Companies should be sure patch the name servers that support their email servers, he said.

MessageLabs’s Wood agreed, adding that users should take steps to encrypt sensitive email traffic, so that even if messages are successfully diverted, they will be difficult to decode. “And you should keep hold of the keys, and be sure reset them when employees leave,” he said.

“This is a long way from over,” Shimel says. “We’ve built a moat around the castle, but there are a lot more issues here, and I’m not aware of any security company that’s directly addressing them all.”

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.

  • IOActive
  • MessageLabs Ltd.
  • StillSecure

    Tim Wilson is Editor in Chief and co-founder of Dark Reading.com, UBM Tech's online community for information security professionals. He is responsible for managing the site, assigning and editing content, and writing breaking news stories. Wilson has been recognized as one ... View Full Bio

    Comment  | 
    Print  | 
    More Insights
  • Comments
    Newest First  |  Oldest First  |  Threaded View
    COVID-19: Latest Security News & Commentary
    Dark Reading Staff 10/30/2020
    'Act of War' Clause Could Nix Cyber Insurance Payouts
    Robert Lemos, Contributing Writer,  10/29/2020
    6 Ways Passwords Fail Basic Security Tests
    Curtis Franklin Jr., Senior Editor at Dark Reading,  10/28/2020
    Register for Dark Reading Newsletters
    White Papers
    Video
    Cartoon
    Current Issue
    How to Measure and Reduce Cybersecurity Risk in Your Organization
    In this Tech Digest, we examine the difficult practice of measuring cyber-risk that has long been an elusive target for enterprises. Download it today!
    Flash Poll
    How IT Security Organizations are Attacking the Cybersecurity Problem
    How IT Security Organizations are Attacking the Cybersecurity Problem
    The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
    Twitter Feed
    Dark Reading - Bug Report
    Bug Report
    Enterprise Vulnerabilities
    From DHS/US-CERT's National Vulnerability Database
    CVE-2020-5425
    PUBLISHED: 2020-10-31
    Single Sign-On for Vmware Tanzu all versions prior to 1.11.3 ,1.12.x versions prior to 1.12.4 and 1.13.x prior to 1.13.1 are vulnerable to user impersonation attack.If two users are logged in to the SSO operator dashboard at the same time, with the same username, from two different identity provider...
    CVE-2020-15703
    PUBLISHED: 2020-10-31
    There is no input validation on the Locale property in an apt transaction. An unprivileged user can supply a full path to a writable directory, which lets aptd read a file as root. Having a symlink in place results in an error message if the file exists, and no error otherwise. This way an unprivile...
    CVE-2020-5991
    PUBLISHED: 2020-10-30
    NVIDIA CUDA Toolkit, all versions prior to 11.1.1, contains a vulnerability in the NVJPEG library in which an out-of-bounds read or write operation may lead to code execution, denial of service, or information disclosure.
    CVE-2020-15273
    PUBLISHED: 2020-10-30
    baserCMS before version 4.4.1 is vulnerable to Cross-Site Scripting. The issue affects the following components: Edit feed settings, Edit widget area, Sub site new registration, New category registration. Arbitrary JavaScript may be executed by entering specific characters in the account that can ac...
    CVE-2020-15276
    PUBLISHED: 2020-10-30
    baserCMS before version 4.4.1 is vulnerable to Cross-Site Scripting. Arbitrary JavaScript may be executed by entering a crafted nickname in blog comments. The issue affects the blog comment component. It is fixed in version 4.4.1.