• United States



Security Vulnerability Found in Visual Studio 2005

Nov 01, 20062 mins
CSO and CISOData and Information Security

A vulnerability in Visual Studio 2005 could let an attacker execute code on a targeted Windows machine, Microsoft said Wednesday.

Danish security vendor Secunia rated the vulnerability as “extremely critical” since it hasn’t been patched and there are unconfirmed reports it’s being exploited, said Thomas Kristensen, chief technology officer for Secunia.

Microsoft said proof-of-concept attack code has been published, and the company could eventually issue a patch after its investigation. The company typically issues patches on the second Tuesday of the month, although it has been known to push out a patch faster depending on the risk of the vulnerability.

“We are aware of the possibility of limited attacks that are attempting to use the reported vulnerability,” wrote Christopher Budd, a security program manager on Microsoft’s Security Center Response blog.

The vulnerability lies in an Active X control called the WMI Object Broker control, contained in the WmiScriptUtils.dll, Microsoft said. For a successful attack, a user would have to be lured to a Web site designed to exploit the flaw. Microsoft cautioned against following links in e-mails from unknown senders, since those could lead to an attacker’s site.

Microsoft posted several mitigating factors that would head off attacks. For example, the particular ActiveX control is not included in the default allow list for Internet Explorer 7.

Also, those who are running Visual Studio 2005 on Windows Server 2003 and Windows Server 2003 Service Pack 1 in their default configurations–with the Enhanced Security Configuration turned on–are not affected, Microsoft wrote.

If an attack was successful, the hacker would only have the same rights as a local user, so Microsoft said those accounts configured with fewer rights than an administrator might cause less of an impact.

Visual Studio is an application development tool from Microsoft.

By Jeremy Kirk, IDG News Service (London Bureau)

Keep checking in at our Security Feed for updated news coverage.