Related topics

Microsoft sees spike in attacks targeting 0day Windows bug

With help like that ...

The number of malicious attacks exploiting an unpatched vulnerability in older versions of Windows has mushroomed over the past week, prompting Microsoft to warn customers to deploy countermeasures until an update is released.

Microsoft said on Wednesday that its security team has detected more than 10,000 distinct computers that have experienced the attack against the bug in the Windows Help and Support Center. The vulnerability, which was disclosed on June 10 by researcher Tavis Ormandy, makes it possible for attackers to remotely install malware on computers running Windows XP and Server 2003 by luring end users to booby-trapped websites.

For the first 10 days following the disclosure, attacks were targeted and relatively few. But over the past week and a half, they have suddenly increased, Holly Stewart, a member of the Microsoft Malware Protection Center, warned here. Geographies with the biggest attack volume are the US, Russia, Portugal, Germany, and Brazil.

Stewart advised vulnerable Windows users who have not implemented one of the countermeasures listed here to strongly consider doing so now.

The surge of attacks appear to be carried out by “seemingly-automated, randomly-generated html and php pages,” Stewart said. When the attacks began, they mostly installed a backdoor known as Obitel, which is used to download other malware. But over time the exploits have marshaled a variety of other trojans, which Microsoft detects as Win32/Swrort.A, Win32/Tedroo.AB, Win32/Oficla.M, and Win32/Neetro.A, among others.

Microsoft has said it's working on an update to patch the gaping security hole. In additional to deploying workarounds, users can find some protection from Security Essentials, Forefront Client Security, and other anti-virus products from Microsoft.

The spike in attacks shows the darker side of so-called full disclosure, which is the belief among some security professionals that all information about vulnerabilities should be communicated as broadly as possible so that individuals are fully informed about risks and companies have an incentive to fix the bugs as soon as possible. It's a position your reporter has regularly and sometimes vociferously advocated. But it also seems fair to say that these attacks probably wouldn't have happened had Ormandy been more reticent. ®

Sponsored: Designing and building an open ITOA architecture