Security Advisor

Was the Flame Malware Spread Microsoft's Fault?

Last week I wrote about the somewhat newly discovered surveillance worm making its way through the Middle East. Well, Microsoft now says that it could have played a part in the distribution of the malware and pleads ignorance with concern to its role.

According to a Microsoft security advisory, the virus took advantage of a flaw in Microsoft's Terminal Server Licensing Services to create unauthentic Microsoft certificates. Once antivirus programs saw that the Flame was certified by Microsoft, the doors were open for it to cause havoc.

Seeing the error in its ways, Microsoft released a security update that will automatically revoke all bogus Microsoft certificates making their way through the wild. If you don't have automatic update on, go ahead and apply that bandage.

However, if you're not on a nation's watch list, and don't originate from Iran, chances are you'll be safe from infection -- this worm's targets have been a small and selective group of individuals that may or may not be in the terrorist industry.

As for Microsoft, while it didn't knowingly give the Flame architects the key to the Internet, it does hold some of the responsibility for the damage caused by it. Or so Andrew Storms, director of security operations for nCircle, believes.

"The discovery of a bug that's been used to circumvent Microsofts secure code certificate hierarchy is a major breach of trust, and it’s a big deal for every Microsoft user," said Storms. "It also underscores the delicate and problematic nature of the trust models behind every Internet transaction."

What do you think? Is it Microsoft's duty to customers to find and fix any bugs that could be used for harm? Or will hackers always find holes in software, no matter how secure it is? Let me know at [email protected]

About the Author

Chris Paoli is the site producer for Redmondmag.com and MCPmag.com.

Featured

  • SameSite Cookie Changes Rolled Back Until Summer

    The Chromium Project announced on Friday that it's delaying enforcement of SameSite cookie changes, and is temporarily rolling back those changes, because of the COVID-19 turmoil.

  • Basic Authentication Extended to 2H 2021 for Exchange Online Users

    Microsoft is now planning to disable Basic Authentication use with its Exchange Online service sometime in the "second half of 2021," according to a Friday announcement.

  • Microsoft Offers Endpoint Configuration Manager Advice for Keeping Remote Clients Patched

    Microsoft this week offered advice for organizations using Microsoft Endpoint Configuration Manager with remote Windows systems that need to get patched, and it also announced Update 2002.

  • Azure Edge Zones Hit Preview

    Azure Edge Zones, a new edge computing technology from Microsoft designed to enable new scenarios for developers and partners, emerged as a preview release this week.

comments powered by Disqus

Office 365 Watch

Sign up for our newsletter.

Terms and Privacy Policy consent

I agree to this site's Privacy Policy.