Microsoft Security Bulletin MS07-052 - Important
Vulnerability in Crystal Reports for Visual Studio Could Allow Remote Code Execution (941522)
Published: | Updated:
Version: 1.1
General Information
Executive Summary
This important security update resolves a publicly disclosed vulnerability. This vulnerability could allow remote code execution if a user opens a specially crafted RPT file. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
This is an important security update for supported editions of Visual Studio that include a custom version of Crystal Reports. Only the specific editions of Visual Studio listed in the Affected Software section are affected because they contain Crystal Reports. For more information, see the subsection, Affected and Non-Affected Software, in this section.
This security update addresses the vulnerability by modifying the way that Crystal Reports for Visual Studio handles RPT files. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
Recommendation: Microsoft recommends that customers apply the security update at the earliest opportunity.
Known Issues: Microsoft Knowledge Base Article 941522 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues.
Affected and Non-Affected Software
The software listed here have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle. Only the listed editions of Visual Studio are affected. Other editions do not need to be updated because they do not contain Crystal Reports and are not vulnerable.
Affected Software
| Software | Edition | Maximum Security Impact | Aggregate Severity Rating | Bulletins Replaced by This Update |
|---|---|---|---|---|
| Visual Studio .NET 2002 Service Pack 1 (KB937057) | Microsoft Visual Studio .NET Enterprise Architect Microsoft Visual Studio .NET Enterprise Developer Microsoft Visual Studio .NET Professional | Remote Code Execution | Important | None |
| Visual Studio .NET 2003 (KB937058) | Microsoft Visual Studio .NET Enterprise Architect 2003 Microsoft Visual Studio .NET Enterprise Developer 2003 Microsoft Visual Studio .NET Professional 2003 | Remote Code Execution | Important | None |
| Visual Studio .NET 2003 Service Pack 1 (KB937059) | Microsoft Visual Studio .NET Enterprise Architect 2003 Microsoft Visual Studio .NET Enterprise Developer 2003 Microsoft Visual Studio .NET Professional 2003 | Remote Code Execution | Important | None |
| Visual Studio 2005 (KB937060) | Microsoft Visual Studio 2005 Professional Edition Microsoft Visual Studio 2005 Team Edition for Software Architects Microsoft Visual Studio 2005 Team Edition for Software Developers Microsoft Visual Studio 2005 Team Suite Microsoft Visual Studio 2005 Team Edition for Software Testers | Remote Code Execution | Important | None |
| Visual Studio 2005 Service Pack 1 (KB937061) | Microsoft Visual Studio 2005 Professional Edition Microsoft Visual Studio 2005 Team Edition for Software Architects Microsoft Visual Studio 2005 Team Edition for Software Developers Microsoft Visual Studio 2005 Team Suite Microsoft Visual Studio 2005 Team Edition for Software Testers | Remote Code Execution | Important | None |
Non-Affected Software
| Operating System |
|---|
| Microsoft Office Outlook 2003 with Business Contact Manager |
| Microsoft Office Outlook 2007 with Business Contact Manager |
Frequently Asked Questions (FAQ) Related to This Security Update
I am using an older release of the software discussed in this security bulletin. What should I do?
The affected software listed in this bulletin have been tested to determine which releases are affected. Other releases are past their support life cycle. To determine the support life cycle for your software release, visit Microsoft Support Lifecycle.
It should be a priority for customers who have older releases of the software to migrate to supported releases to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle. For more information about the extended security update support period for these software releases, visit the Microsoft Product Support Services Web site.
Customers who require custom support for older software must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ.
Vulnerability Information
Severity Ratings and Vulnerability Identifiers
| Affected Software | Crystal Reports RPT Processing Vulnerability – CVE-2006-6133 | Aggregate Severity Rating |
|---|---|---|
| Visual Studio .NET 2002 Service Pack 1 | Important Remote Code Execution | Important |
| Visual Studio .NET 2003 | Important Remote Code Execution | Important |
| Visual Studio .NET 2003 Service Pack 1 | Important Remote Code Execution | Important |
| Visual Studio 2005 | Important Remote Code Execution | Important |
| Visual Studio 2005 Service Pack 1 | Important Remote Code Execution | Important |
Crystal Reports RPT Processing Vulnerability – CVE-2006-6133
A remote code execution vulnerability exists in the way Crystal Reports for Visual Studio handles malformed RPT files. An attacker could exploit the vulnerability by sending an affected user a malformed RPT file as an e-mail attachment, or hosting the file on a malicious or compromised Web site.
An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2006-6133.
Mitigating Factors for Crystal Reports RPT Processing Vulnerability – CVE-2006-6133
Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factor may be helpful in your situation:
- An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
- In default configurations, RPT files are not registered to open with Crystal Reports for Visual Studio. Without the association, RPT files will not open using the affected software component when the user double-clicks on them.
Workarounds for Crystal Reports RPT Processing Vulnerability – CVE-2006-6133
Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:
- Remove the Crystal Reports for Visual Studio feature from Visual Studio
Removing the Crystal Reports for Visual Studio feature will prevent users from opening Crystal Reports files.
- Use Add/Remove Programs
- Click Start, click Control Panel, click Add/Remove Programs.
- Find your installation of Visual Studio and select it.
- Click Add/Remove Features.
- Uncheck the box next to Crystal Reports for Visual Studio.
- Click Update to remove the feature.
- Use the original installation media
- Insert the original installation CD for Visual Studio into your drive.
- Wait for the setup menu to appear. Click Add/Remove Features.
- Uncheck the box next to Crystal Reports for Visual Studio.
- Click Update to remove the feature.
Impact of workaround: Crystal Reports files will not open.
How to undo the workaround: Add the Crystal Reports for Visual Studio component using the Add/Remove Programs menu and select the Crystal Reports for Visual Studio feature.
- Use Add/Remove Programs
- For affected editions of Visual Studio 2002 and Visual Studio 2003, unregister craxddrt20.dll
Administrators can help protect users by unregistering a key DLL file, which loads RPT files. This will prevent users from opening RPT files.
- Log on as a user with administrator privileges.
- Click Start, click Run, type cmd, and then click OK.
- Type the following command at a command prompt:
regsvr32.exe –u “\Program Files\Common Files\Crystal Decisions\1.0\Bin\craxddrt20.dll”
Impact of workaround: Crystal Reports files will not open.
How to undo the workaround: Re-register craxddrt20.dll. Type the following command at a command prompt:
regsvr32.exe “\Program Files\Common Files\Crystal Decisions\1.0\Bin\craxddrt20.dll” - For affected editions of Visual Studio 2005, unregister craxddrt.dll
Administrators can help protect users by unregistering a key DLL file, which loads RPT files. This will prevent users from opening RPT files.
- Log on as a user with administrator privileges.
- Start, click Run, type cmd, and then click OK.
- Type the following command at a command prompt:
regsvr32.exe –u “\Program Files\Common Files\Business Objects\2.7\Bin\craxddrt.dll”
Impact of workaround: Crystal Reports files will not open.
How to undo the workaround: Re-register craxddrt.dll. Type the following command at a command prompt:
regsvr32.exe “\Program Files\Common Files\Business Objects\2.7\Bin\craxddrt.dll” - For affected editions of Visual Studio .NET 2002 and Visual Studio .NET 2003, modify Access Control List on craxddrt20.dll
To modify the Access Control List (ACL) on craxddrt20 to be more restrictive, follow these steps:
- Log on as a user with administrator privileges.
- Click Start, click Run, type cmd, and then click OK.
- Document the current ACLs that are on the file (including inheritance settings) for future reference in case you have to undo this modification. To view the ACLs, type the following:
cacls “\Program Files\Common Files\Crystal Decisions\1.0\Bin\craxddrt20.dll” - To deny the “everyone” group access to the file, type the following command at a command prompt:
cacls “\Program Files\Common Files\Crystal Decisions\1.0\Bin\craxddrt20.dll” /E /D Everyone
Impact of workaround: Crystal Reports files will not open.
How to undo the workaround: Type the following command at a command prompt:
cacls “\Program Files\Common Files\Crystal Decisions\1.0\Bin\craxddrt20.dll” /E /R Everyone - For affected editions of Visual Studio 2005, modify the Access Control List on craxddrt.dll
To modify the Access Control List (ACL) on craxddrt.dll to be more restrictive, follow these steps:
- Log on as a user with administrator privileges.
- Click Start, click Run, type cmd, and then click OK.
- Document the current ACLs that are on the file (including inheritance settings) for future reference in case you have to undo this modification. To view the ACLs, type the following:
cacls “\Program Files\Common Files\Business Objects\2.7\Bin\craxddrt.dll”] - To deny the “everyone” group access to the file, type the following command at a command prompt:
cacls “\Program Files\Common Files\Business Objects\2.7\Bin\craxddrt.dll” /E /D Everyone
Impact of workaround: Crystal Reports files will not open.
How to undo the workaround: Type the following command at a command prompt:
cacls “\Program Files\Common Files\Business Objects\2.7\Bin\craxddrt.dll” /E /R Everyone
FAQ for Crystal Reports RPT Processing Vulnerability – CVE-2006-6133
What is the scope of the vulnerability?
This is a remote code execution vulnerability. If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
What causes the vulnerability
The vulnerability exists in the way that Crystal Reports handles specially crafted RPT files, potentially allowing arbitrary code to be executed.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run code on the affected system.
How could an attacker exploit the vulnerability?
An attacker could exploit this vulnerability by sending a specially crafted RPT file as an attachment in e-mail and then persuading the user to open the attachment. If the user opened the attachment in an affected edition of Visual Studio, the attacker could cause arbitrary code to run in the security context of the locally logged-on user.
What is Crystal Reports?
Crystal Reports is a software offering from Business Objects. Microsoft redistributes a custom version of Crystal Reports in certain editions Visual Studio .NET 2002, Visual Studio .NET 2003, and Visual Studio 2005.
Why is this update for Visual Studio?
The vulnerability addressed in this security update is for a version of Crystal Reports that is distributed with Visual Studio. Customers who install the affected editions of Visual Studio are potentially at risk and should update their systems.
I am a third-party application developer and I use Crystal Reports in my application. Is my application vulnerable and how do I update it?
Visual Studio is the only Microsoft development platform affected by this security update. This Bulletin provides links to download the update for affected editions of Visual Studio. If you have redistributed any file listed in the File Information subsection, you should issue an updated version of your application to your customers with the updated versions of these files included in this security update.
What systems are primarily at risk from the vulnerability?
Workstations and terminal servers that have an affected edition of Visual Studio installed are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.
What does the update do?
The update removes the vulnerability by adding overflow validations to the handling of RPT files.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. This vulnerability has been publicly disclosed. It has been assigned Common Vulnerability and Exposure number CVE-2006-6133. It also has been named Business Objects Crystal Reports Stack Overflow Vulnerability by the larger security community.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had seen examples of proof of concept code published publicly but had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.
Update Information
Detection and Deployment Tools and Guidance
Manage the software and security updates you need to deploy to the servers, desktop, and mobile computers in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.
Security updates are available from Microsoft Update, Windows Update, and Office Update. Security updates are also available at the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch". Finally, security updates can be downloaded from the Windows Update Catalog. For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166.
Detection and Deployment Guidance
Microsoft has provided detection and deployment guidance for this month’s security updates. This guidance will also help IT professionals understand how they can use various tools to help deploy the security update, such as Windows Update, Microsoft Update, Office Update, the Microsoft Baseline Security Analyzer (MBSA), the Office Detection Tool, Microsoft Systems Management Server (SMS), the Extended Security Update Inventory Tool, and the Enterprise Update Scan Tool (EST). For more information, see Microsoft Knowledge Base Article 910723.
Microsoft Baseline Security Analyzer and Enterprise Update Scan Tool (EST)
Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA, visit Microsoft Baseline Security Analyzer.
MBSA 1.2.1 does not support detection for this security update. The Enterprise Update Scan Tool does, and is what customers can use instead of MBSA 1.2.1. For download links and more information about the version of EST that is being released this month, see Microsoft Knowledge Base Article 894193. SMS customers should also see the heading, Systems Management Server, for more information about SMS and EST.
The following table provides the MBSA and EST detection summary for this security update.
| Software | MBSA 1.2.1 | EST | MBSA 2.0.1 |
|---|---|---|---|
| Visual Studio .NET 2002 Service Pack 1 | No | Yes | No |
| Visual Studio .NET 2003 | No | Yes | No |
| Visual Studio .NET 2003 Service Pack 1 | No | Yes | No |
| Visual Studio 2005 | No | Yes | Yes |
| Visual Studio 2005 Service Pack 1 | No | Yes | Yes |
For more information about MBSA, visit the Microsoft Baseline Security Analyzer. For more information about the software that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660.
Windows Server Update Services
By using Windows Server Update Services (WSUS), administrators can deploy the latest important updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 to Windows 2000 and later operating systems. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site.
Systems Management Server
The following table provides the SMS detection and deployment summary for this security update.
| Software | SMS 2.0 | SMS 2003 |
|---|---|---|
| Visual Studio .NET 2002 Service Pack 1 | Yes (with EST) | Yes |
| Visual Studio .NET 2003 | Yes (with EST) | Yes |
| Visual Studio .NET 2003 Service Pack 1 | Yes (with EST) | Yes |
| Visual Studio 2005 | Yes (with EST) | Yes |
| Visual Studio 2005 Service Pack 1 | Yes (with EST) | Yes |
SMS 2.0 and SMS 2003 Software Update Services (SUS) Feature Pack can use MBSA 1.2.1 for detection and therefore have the same limitation listed earlier relating to programs that MBSA 1.2.1 does not detect.
For SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about SUIT, visit the following Microsoft Knowledge Base Article 894154. For more information about the limitations of SUIT, see Microsoft Knowledge Base Article 306460. The SMS SUS Feature Pack also includes the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.
For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, visit the following Microsoft Web site. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.
For more information about SMS, visit the Systems Management Server.
For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.
Security Update Deployment
Affected Software
For information about the specific security update for your affected software, click the appropriate link:
Visual Studio .NET 2002 Service Pack 1
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | The update for this issue may be included in a future update rollup |
| Deployment | |
| Installing without user intervention | VS7.0sp1-KB937057-x86 /q |
| Installing without restarting | VS7.0sp1-KB937057-x86 /q |
| Update log file | Not applicable |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. |
| Hotpatching | Not applicable |
| Removal Information | Use Add or Remove Program tool in Control Panel. |
| File Information | See the next subsection, File Information for the full file manifest |
| Registry Key Verification | HKEY_LOCAL_MACHINE\Software\Microsoft\Updates\Visual Studio\7.0\M937057 "Installed" = DWORD:1 |
File Information
The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
For all affected editions of Visual Studio .NET 2002 Service Pack 1:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| Craxddrt20.dll | 9.1.2.1871 | 10-Jul-2007 | 02:58 | 8,926,800 |
| Crdesigner.dll | 9.1.0.2004 | 10-Jul-2007 | 02:58 | 484,944 |
| Crpe32.dll | 9.1.2.1871 | 10-Jul-2007 | 02:58 | 5,355,080 |
| Crqe.dll | 9.1.1.473 | 10-Jul-2007 | 02:58 | 1,193,480 |
Note For a complete list of supported versions and editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.
Deployment Information
Installing the Update
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options |
| Setup Modes | |
| /q | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Install Options | |
| /I | Install (default action) |
| /U | Uninstall |
| /Xp[:path] | Extract the package to the specified directory |
| Restart Options | |
| /q | Does not restart when installation has completed |
| Logging Options | |
| /l <LogFile> | Generate Log File |
| /l[d|p|f] <logfile> | d – Log package details p – Log affected products f – Log included files |
Verifying That the Update Has Been Applied
- Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
- File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed.
- On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
- Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.
These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.
Visual Studio .NET 2003
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | The update for this issue may be included in a future update rollup |
| Deployment | |
| Installing without user intervention | Visual Studio .NET 2003 (KB937058): VS7.1-KB937058-x86-INTL /q |
| Visual Studio .NET 2003 Service Pack 1 (KB937059): VS7.1sp1-KB937059-x86-INTL /q | |
| Installing without restarting | Visual Studio .NET 2003 (KB937058): VS7.1-KB937058-x86-INTL /q |
| Visual Studio .NET 2003 Service Pack 1 (KB937059): VS7.1sp1-KB937059-x86-INTL /q | |
| Update log file | Not applicable |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. |
| Hotpatching | Not applicable |
| Removal Information | Use Add or Remove Program tool in Control Panel. |
| File Information | See the next subsection, File Information, for the full file manifest |
| Registry Key Verification | Visual Studio .NET 2003 (KB937058): HKEY_LOCAL_MACHINE\Software\Microsoft\Updates\Visual Studio\7.1\M937058 "Installed" = DWORD:1 |
| Visual Studio .NET 2003 Service Pack 1 (KB937059): HKEY_LOCAL_MACHINE\Software\Microsoft\Updates\Visual Studio\7.1\M937059 "Installed" = DWORD:1 |
File Information
The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
For all affected editions of Visual Studio .NET 2003 (KB937058):
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| Craxddrt20.dll | 9.1.2.1871 | 09-Jul-2007 | 21:58 | 8,926,800 |
| Crdesigner.dll | 9.1.2.1871 | 09-Jul-2007 | 21:58 | 472,656 |
| Crpe32.dll | 9.1.2.1871 | 09-Jul-2007 | 21:58 | 5,355,080 |
| Crqe.dll | 9.1.1.473 | 09-Jul-2007 | 21:58 | 1,193,480 |
For all affected editions of Visual Studio .NET 2003 Service Pack 1 (KB937059):
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| Craxddrt20.dll | 9.1.2.1871 | 09-Jul-2007 | 21:58 | 8,926,800 |
| Crdesigner.dll | 9.1.2.1871 | 09-Jul-2007 | 21:58 | 472,656 |
| Crpe32.dll | 9.1.2.1871 | 09-Jul-2007 | 21:58 | 5,355,080 |
| Crqe.dll | 9.1.1.473 | 09-Jul-2007 | 21:58 | 1,193,480 |
Note For a complete list of supported versions and editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.
Deployment Information
Installing the Update
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options |
| Setup Modes | |
| /q | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Install Options | |
| /I | Install (default action) |
| /U | Uninstall |
| /Xp[:path] | Extract the package to the specified directory |
| Restart Options | |
| /q | Does not restart when installation has completed |
| Logging Options | |
| /l <LogFile> | Generate Log File |
| /l[d|p|f] <logfile> | d – Log package details p – Log affected products f – Log included files |
Verifying That the Update Has Been Applied
- Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
- File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed.
- On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
- Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.
These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.
Visual Studio 2005
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | The update for this issue may be included in a future update rollup |
| Deployment | |
| Installing without user intervention | Visual Studio 2005 (KB937060): VS80-KB937060-x86 /q |
| Visual Studio 2005 Service Pack 1 (KB937061): VS80sp1-KB937061-x86 /q | |
| Installing without restarting | Visual Studio 2005 (KB937060): VS80-KB937060-x86 /norestart |
| Visual Studio 2005 Service Pack 1 (KB937061): VS80sp1-KB937061-x86 /norestart | |
| Update log file | Not applicable |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. |
| Hotpatching | Not applicable |
| Removal Information | Use Add or Remove Program tool in Control Panel. |
| File Information | See the next subsection, File Information for the full file manifest |
| Registry Key Verification | Visual Studio 2005 (KB937060): HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft Visual Studio 2005 Professional Edition - ENU\KB937060 "Installed" = DWORD:1 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft Visual Studio 2005 Team Edition for Software Architects - ENU\KB937060 "Installed" = DWORD:1 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft Visual Studio 2005 Team Edition for Software Developers - ENU\KB937060 "Installed" = DWORD:1 |
| Visual Studio 2005 Service Pack 1 (KB937061): HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft Visual Studio 2005 Professional Edition - ENU\KB937061 "Installed" = DWORD:1 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft Visual Studio 2005 Team Edition for Software Architects - ENU\KB937061 "Installed" = DWORD:1 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft Visual Studio 2005 Team Edition for Software Developers - ENU\KB937061 "Installed" = DWORD:1 |
File Information
The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
For all affected editions of Visual Studio 2005 (KB937060):
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| Craxddrt.dll | 10.2.0.1222 | 23-Jun-2007 | 04:22 | 14,288,656 |
| Crdesigner.dll | 10.2.0.1222 | 23-Jun-2007 | 04:22 | 841,488 |
| Crpe32.dll | 10.2.0.1222 | 23-Jun-2007 | 04:22 | 9,525,008 |
For all affected editions of Visual Studio 2005 Service Pack 1 (KB937061):
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| Craxddrt.dll | 10.2.0.1222 | 23-Jun-2007 | 04:04 | 14,288,656 |
| Crdesigner.dll | 10.2.0.1222 | 23-Jun-2007 | 04:04 | 841,488 |
| Crpe32.dll | 10.2.0.1222 | 23-Jun-2007 | 04:04 | 9,525,008 |
Note For a complete list of supported versions and editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.
Deployment Information
Installing the Update
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /? /h /help | Displays the usage dialog box. |
| Setup Modes | |
| /q[n|b|r|f] | Sets usage interface level. n – No UI b – Basic UI r – Reduced UI f – Full UI (default) |
| Install Options | |
| /extract [directory] | Extract the package to the specified directory |
| Restart Options | |
| /norestart | Does not restart when installation has completed |
| /promptrestart | Prompts the user for restart if necessary |
| /forcerestart | Always restart the computer after installation |
| Logging Options | |
| /l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <logfile> | i – Status messages w - Nonfatal warnings e - All error messages a - Start up of actions r - Action-specific records u - User requests c - Initial UI parameters m - Out-of-memory or fatal exit information o - Out-of-disk-space messages p - Terminal properties v - Verbose output x - Extra debugging information + - Append to existing log file ! - Flush each line to the log * - Log all information, except for v and x options |
| /log <LogFile> | Equivalent of /l* <LogFile> |
Verifying That the Update Has Been Applied
- Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
- File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed.
- On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
- Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.
These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.
Other Information
Support
- 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.
Disclaimer
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.
Revisions
- V1.0 (September 11, 2007): Bulletin published.
- V1.1 (September 19, 2007): Bulletin updated: The executable filename for Visual Studio 2003 Service Pack 1 has been correctly updated to VS7.1sp1-KB937059-x86-INTL in the corresponding Reference Table under “Security Update Deployment”.