Microsoft admits it knew about, but didn't patch, bugs

Microsoft's security team Tuesday acknowledged that it knew of bugs in its Jet Database Engine as far back as 2005 but did not patch the problems because it thought it had blocked the obvious attack vector.

A researcher at Symantec Corp. said Microsoft should have fixed the flaws years ago.

In a post to the Microsoft Security Research Center (MSRC) blog late Monday afternoon , Mike Reavey, the MSRC's operations manager, admitted that outside researchers had notified Microsoft in 2005 and 2007 of separate bugs in Jet, a Windows component that provides data access to applications such as Microsoft Access and Visual Basic.

In both cases, Microsoft had told the researchers that it would not fix the flaw because it considered users safe. Outlook blocked the .mdb file format from being opened, Exchange servers stripped them from incoming e-mail and Internet Explorer issued warnings when users clicked on such files, said Reavey in explaining Microsoft's decision.

The company hadn't thought of the attack strategy now being used by hackers, however. "Everything changed with the discovery of this new attack vector that allowed an attacker to load an MDB file via opening a Microsoft Word document," he said. "The previous guidance does not work against this new attack. So that's why we alerted customers to these attacks and are re-investigating Jet parsing flaws -- this is a new attack vector discovered that we didn't know about previously."

Attackers are, in fact, doing an end-run around Outlook, researchers at Symantec said last week when they released findings that prompted Microsoft to issue a security advisory warning users running Word on Windows 2000, XP and Server 2003 SP1 to take defensive steps.

One researcher said Microsoft could have done more earlier to prevent the sudden scramble for a fix.

"I can't count the number of times we've seen this in the past with a Microsoft product," said Oliver Friedrichs , a director with Symantec's security response team. "Clearly, there should have been more concern from Microsoft in the first place. There have been two vulnerabilities, one in 2005 and another in 2007, and both were left unpatched.

For more enterprise computing news, visit Computerworld. Story copyright Computerworld, Inc.