As Microsoft patched the Internet Explorer (IE) vulnerability that was used to break into Google's network, it also acknowledged that it had known of the bug since August 2009, when an Israeli security company reported the flaw.
"As part of [our] investigation, we also determined that the vulnerability was the same as a vulnerability responsibly reported to us and confirmed in early September," said Jerry Bryant, a senior program manager with the Microsoft Security Response Center, on the MSRC blog today.
[ Learn how to secure your systems with Roger Grimes' Security Adviser blog and Security Central newsletter, both from InfoWorld. | Grimes also explains how to stop data leaks in an enlightening 30-minute webcast, Data Loss Prevention, which covers the tools and techniques used by experienced security pros. ]
The MS10-002 bulletin that accompanied the IE update credited Meron Sellem of BugSec for reporting the bug that has raised a ruckus since Google accused Chinese cybercriminals with hacking its network.
Sellem said that BugSec, a penetration testing and security firm in Rishon LeZion, Israel, reported the vulnerability to Microsoft on Aug. 26, not in September as Microsoft indicated. And he was critical of Microsoft for taking this long to release a patch. "I think yes, it took too long," he said. "But Microsoft is a big organization and we don't know how much time it takes them. We asked them why it was taking such a long time, and they said it was because of the testing they had to do."
Andrew Storms, director of security operations at nCircle Network Security, said the fact that Microsoft knew of the browser's vulnerability months before it crafted a patch -- months before Chinese criminals used the flaw -- shouldn't come as a shock.
"It's pretty par for the course, really," said Storms. "We know that patches sit for a good month or so in QA [quality assurance] at Microsoft. So if it was reported to Microsoft in September, it might not have been added to the [patch] cycle until October, and the code not written until November. A February release isn't crazy then."
Storms refused to use hindsight to say that Microsoft was tardy to the party. "Unless you have real evidence that it's being used, you can't take that into account when you prioritize patches," he argued. "You take into account the skill level necessary to exploit it. But if it's responsibly disclosed, you have to assume that it's not going to release [publicly]. And without partners saying that they're seeing signs of it being exploited, Microsoft probably thought they could just roll it into their normal IE release cycle."