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 firstname.lastname@example.org.