Lucene search

K
securityvulnsSecurityvulnsSECURITYVULNS:DOC:17980
HistorySep 11, 2007 - 12:00 a.m.

Microsoft Security Bulletin MS07-052 - Important

2007-09-1100:00:00
vulners.com
23

Microsoft Security Bulletin MS07-052 - Important
Vulnerability in Crystal Reports for Visual Studio Could Allow Remote Code Execution (941522)
Published: September 11, 2007

Version: 1.0
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: None.
Top of sectionTop of section
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
Top of sectionTop of section

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.
Top of sectionTop of section
Vulnerability Information

Severity Ratings and Vulnerability Identifiers
Vulnerability Severity Rating and Maximum Security Impact by Affected Software
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
Top of sectionTop of section

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.
Top of sectionTop of section

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.

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
Top of sectionTop of section

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.

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.
Top of sectionTop of section
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.
Top of sectionTop of section
Revisions

V1.0 (September 11, 2007): Bulletin published.

Related for SECURITYVULNS:DOC:17980