Microsoft Security Bulletin MS06-073 - Critical
Vulnerability in Visual Studio 2005 Could Allow Remote Code Execution (925674)
Who Should Read this Document: Customers who use Microsoft Visual Studio 2005
Impact of Vulnerability: Remote Code Execution
Maximum Severity Rating: Critical
Recommendation: Customers should apply the update immediately
Security Update Replacement: None
Caveats: Microsoft Knowledge Base Article 925674 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues. For more information, see Microsoft Knowledge Base Article 925674.
Tested Software and Security Update Download Locations:
- Microsoft Visual Studio 2005 — Download the update
- Visual Studio 2005 Standard Edition
- Visual Studio 2005 Professional Edition
- Visual Studio 2005 Team Suite
- Visual Studio 2005 Team Edition for Developers
- Visual Studio 2005 Team Edition for Architects
- Visual Studio 2005 Team Edition for Testers
- Microsoft Visual Studio 2005
- Visual Basic 2005 Express Edition
- Visual C++ 2005 Express Edition
- Visual C# Express Edition
- Visual J# Express Edition
- Visual Web Developer Express Edition
- Visual Studio 2005 Tools For Office
- Visual Studio 2005 Team Explorer
- Visual Studio 2005 Team Foundation Dual-Server
- Visual Studio 2005 Team Foundation Single Server
- Visual Studio 2005 Team Foundation Proxy
- Visual Studio 2005 Team Foundation Build
- Visual Studio 2005 Premier Partner Edition
- Microsoft Visual Studio 6.0 Service Pack 6
- Microsoft Visual Studio .NET 2002 Service Pack 1
- Microsoft Visual Studio .NET 2003 Service Pack 1
Note Not all versions of Visual Studio 2005 include the affected file. If you do not have wmiscriptutils.dll on your system you are not affected by this vulnerability.
The software in this list has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.
Microsoft thanks the following for working with us to help protect customers:
- TippingPoint and the Zero Day Initiative, for originally reporting the WMI Object Broker Vulnerability - CVE-2006-4704.
Obtaining Other Security Updates:
Updates for other security issues are available at the following locations:
- Security updates are available at the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch."
- Updates for consumer platforms are available at the Microsoft Update Web site.
- Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.
- International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.
- The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.
- TechNet Update Management Center
- Microsoft Software Update Services
- Microsoft Windows Server Update Services
- Microsoft Baseline Security Analyzer (MBSA)
- Windows Update
- Microsoft Update
- Windows Update Catalog: For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166.
- Office Update
Software Update Services:
By using Microsoft Software Update Services (SUS), administrators can quickly and reliably deploy the latest critical updates and security updates to Windows 2000 and Windows Server 2003-based servers, and to desktop systems that are running Windows 2000 Professional or Windows XP Professional.
For more information about how to deploy security updates by using Software Update Services, visit the Software Update Services Web site.
Windows Server Update Services:
By using Windows Server Update Services (WSUS), administrators can quickly and reliably deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 onto Windows 2000 and later operating systems.
For more information about how to deploy security updates using Windows Server Update Services, visit the Windows Server Update Services Web site.
Systems Management Server:
Microsoft Systems Management Server (SMS) delivers a highly configurable enterprise solution for managing updates. By using SMS, administrators can identify Windows-based systems that require security updates and can perform controlled deployment of these updates throughout the enterprise with minimal disruption to end users. For more information about how administrators can use SMS 2003 to deploy security updates, visit the SMS 2003 Security Patch Management Web site. SMS 2.0 users can also use Software Updates Service Feature Pack to help deploy security updates. For information about SMS, visit the SMS Web site.
Note SMS uses the Microsoft Baseline Security Analyzer, the Microsoft Office Detection Tool, and the Enterprise Update Scan Tool to provide broad support for security bulletin update detection and deployment. Some software updates may not be detected by these tools. Administrators can use the inventory capabilities of the SMS in these cases to target updates to specific systems. For more information about this procedure, visit the following Web site. Some security updates require administrative rights following a restart of the system. Administrators can use the Elevated Rights Deployment Tool (available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 Administration Feature Pack) to install these updates.
The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
- V1.0 (December 12, 2006): Bulletin published.