News

DNS Problem Is 'Important' To Patch, Microsoft Says

Microsoft issued a formal security advisory with an "urgent warning" to patch a general Domain Name System vulnerability that can enable spoofing attacks.

Microsoft issued a formal security advisory on Friday addressing what IT security pros are calling an "urgent warning" to patch a general Domain Name System (DNS) vulnerability that can enable spoofing attacks. Redmond recommends installing a previously released "important" DNS patch as soon as possible.

The advisory comes almost immediately after H.D. Moore, a hacker and researcher who created the Metasploit vulnerability testing framework, published the attack code in two parts on Wednesday and late Thursday. The code was posted at several security mailing lists and at the Computer Academic Underground Web site.

According to the summary of the exploits, the first one enables a hacker to corrupt the cache in a DNS server. The other exploit is multifaceted and rotates, giving the attacker a shot at a larger amount of domain names through a single entry. Experts say the latter exploit could result in thousands of fake addresses inserted into a DNS server's cache.

In its latest bulletin, Microsoft noted that "attacks are likely imminent" because of the availability of exploit code.

"Since the coordinated release of these updates, the threat to DNS systems has increased due to a greater public understanding of the attacks, as well as detailed exploit code being published on the Internet," the advisory stated.

Reacting to the advisory, IT security pros are saying that Microsoft's statements vindicate the assertions of critics who thought the risk considerations regarding the DNS patch were underplayed.

"While Microsoft admits no active attacks on their radar, and they labeled the patch as 'important,' they are also subtlety saying that everyone needs to patch now because the risk is pretty large," said Andrew Storms, director of security for San Francisco-based nCircle, in an interview with Redmondmag.com on Friday.

IT security pros do admit that the DNS discourse and subsequent exploit release spiraled faster and further than Microsoft could have anticipated.

"The magnitude of the big-picture problem is probably more clear now than when Microsoft released the patch, especially now that exploit code is out and has the capability of significant disruption of all DNS-dependent network activity," said Don Leatham, director of solutions and strategy at Lumension Security in Scottsdale, Ariz.

Leatham suggested scrutiny of the fine print in Microsoft's latest DNS security bulletin.

"We've not seen an inordinate number of inquires on the installation issues. However people should pay special attention to the FAQ for this bulletin, as it has been updated multiple times as issues have been discovered."

While Microsoft touts its DNS vulnerability patch as a safe haven, there are still some issues with actually getting it installed in some Windows programs.

About the Author

Jabulani Leffall is an award-winning journalist whose work has appeared in the Financial Times of London, Investor's Business Daily, The Economist and CFO Magazine, among others.

Featured

  • Microsoft Starting To Roll Out New Excel Connected Data Types

    Microsoft on Thursday announced some Excel and Power BI enhancements that add "connected data types" on top of the standard strings and numbers options.

  • Windows 10 Users Getting New Process for Finding Optional Driver Updates

    Accessing Windows 10 drivers classified as "optional updates" will be more of a manual seek-and-install type of experience, starting on Nov. 5, 2020, Microsoft explained in a Wednesday announcement.

  • Microsoft Changes Privacy Platform Name to SmartNoise

    Microsoft Research has changed the name of its "differential privacy" platform from "WhiteNoise" to "SmartNoise," according to a Wednesday announcement.

  • Why Restarting a Failed SCVMM Job Might Be a Bad Idea

    Occasionally, restarting a failed System Center Virtual Machine Manager job can leave your virtualization infrastructure in an unknown state. Here's how to avoid that.

comments powered by Disqus