Hackers are now exploiting the zero-day Windows vulnerability that a Google engineer took public last week, Microsoft confirmed today.
Although Microsoft did not share details of the attack, other researchers filled in the blanks.
A compromised website is serving an exploit of the bug in Windows' Help and Support Center to hijack PCs running Windows XP, said Graham Cluley, a senior technology consultant at antivirus vendor Sophos. Cluley declined to identify the site, saying only that it was dedicated to open-source software.
"It's a classic drive-by attack," said Cluley, referring to an attack that infects a PC when its user simply visits a malicious or compromised site. The tactic was one of two that Microsoft said last week were the likely attack avenues. The other: Convincing users to open malicious e-mail messages.
According to Microsoft, the exploit has since been scrubbed from the hacked Web site, but it expects more to surface. "We do anticipate future exploitation given the public disclosure of full details of the issue," said Jerry Bryant. Microsoft's group manager of response communications.
The vulnerability was disclosed last Thursday by Tavis Ormandy, a security engineer who works for Google. Ormandy, who also posted proof-of-concept attack code, defended his decision to reveal the flaw only five days after reporting it to Microsoft -- a move that Microsoft and other researchers questioned.
Today, Cluley called Ormandy's action "utterly irresponsible," and in a blog post asked, "Tavis Ormandy - are you pleased with yourself?"
The five-day stretch between the day Ormandy reported the bug to Microsoft and when he publicly disclosed the flaw stuck in Cluley's craw. "Five days isn't enough time to expect Microsoft to develop a fix, which has to be tested thoroughly to ensure it doesn't cause more problems than it intends to correct," Cluley said.
In a message on Twitter last week, Ormandy said that he released the information because Microsoft would not commit to producing a patch within 60 days. "I'm getting pretty tired of all the '5 days' hate mail. Those five days were spent trying to negotiate a fix within 60 days," Ormandy said on Saturday .
Microsoft confirmed that its security team had discussed a patch schedule with Ormandy.
"We were in the early phases of the investigation and communicated [to him] on 6/7 that we would not know what our release schedule would be until the end of the week," said Bryant. "We were surprised by the public release of details on the 9th."
Microsoft issued a security advisory on the vulnerability last Thursday that acknowledged the bug and offered up a manual workaround it said would protect users against attack. The next day, it posted a "Fix it" tool that automatically unregisters the HCP protocol handler, a move Microsoft said "would help block known attack vectors before a security update is available."
The in-the-wild attack code is very similar to the proof-of-concept that Ormandy published last week, said Cluley.
That didn't surprise another security expert. "Given the amount of detail that was released, it's a 'script kiddie' kind of exploit at this point," said Andrew Storms, director of security operations at nCircle Security.
The fact that an exploit based on Ormandy's code was published June 10 for the open-source Metasploit hacking toolkit probably was also a factor, said Storms in an instant message exchange. "No surprise at all there," he said. "There is a large community of people submitting to the Metasploit project."
Microsoft said that the current exploits work against Windows XP machines, but added that Windows Server 2003, the other OS containing the flaw, was safe for the moment. "Windows Server 2003 customers are not currently at risk from the Win Help issue based on the attack samples we have analysed," the company's security team wrote on Twitter at 1.30pmET.
The next regularly-scheduled Microsoft security updates are to ship July 13, but the company occasionally departs from its monthly practice with so-called "out-of-band" emergency updates.
Microsoft declined to comment on whether it would now step up its patch process to produce a fix before July 13. "We continue to monitor the threat landscape and will keep customers updated via our blog at and our Twitter handle ," said Bryant in an email to Computerworld.