The following security advisory is sent to the securiteam mailing list, and can
be found at the SecuriTeam web site: http://www.securiteam.com
- - promotion
The SecuriTeam alerts list - Free, Accurate, Independent.
Get your security news from a reliable source.
http://www.securiteam.com/mailinglist.html
- - - - - - - - -
Vulnerability in Crystal Reports for Visual Studio Allows Code Execution
(MS07-052)
------------------------------------------------------------------------
SUMMARY
A 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.
DETAILS
Affected and Non-Affected Software:
* Visual Studio .NET 2002 Service Pack 1
* Visual Studio .NET 2003
* Visual Studio .NET 2003 Service Pack 1
* Visual Studio 2005
* Visual Studio 2005 Service Pack 1
Non-Affected Software:
* Microsoft Office Outlook 2003 with Business Contact Manager
* Microsoft Office Outlook 2007 with Business Contact Manager
Crystal Reports RPT Processing Vulnerability:
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
<http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-6133>
CVE-2006-6133.
Mitigating Factors for Crystal Reports RPT Processing Vulnerability:
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:
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
1. Click Start, click Control Panel, click Add/Remove Programs.
2. Find your installation of Visual Studio and select it.
3. Click Add/Remove Features.
4. Uncheck the box next to Crystal Reports for Visual Studio.
5. Click Update to remove the feature.
Use the original installation media
1. Insert the original installation CD for Visual Studio into your drive.
2. Wait for the setup menu to appear. Click Add/Remove Features.
3. Uncheck the box next to Crystal Reports for Visual Studio.
4. 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.
1. Log on as a user with administrator privileges.
2. Click Start, click Run, type cmd, and then click OK.
3. 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.
1. Log on as a user with administrator privileges.
2. Start, click Run, type cmd, and then click OK.
3. 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:
1. Log on as a user with administrator privileges.
2. Click Start, click Run, type cmd, and then click OK.
3. 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
4. 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:
1. Log on as a user with administrator privileges.
2. Click Start, click Run, type cmd, and then click OK.
3. 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
]
4. 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:
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.
ADDITIONAL INFORMATION
The information has been provided by Microsoft Security Bulletin MS07-052.
The original article can be found at:
<http://www.microsoft.com/technet/security/bulletin/ms07-052.mspx>
http://www.microsoft.com/technet/security/bulletin/ms07-052.mspx
========================================
This bulletin is sent to members of the SecuriTeam mailing list.
To unsubscribe from the list, send mail with an empty subject line and body to:
list-unsubscribe@securiteam.com
In order to subscribe to the mailing list, simply forward this email to:
list-subscribe@securiteam.com
====================
====================
DISCLAIMER:
The information in this bulletin is provided "AS IS" without warranty of any
kind.
In no event shall we be liable for any damages whatsoever including direct,
indirect, incidental, consequential, loss of business profits or special
damages.
