Export (0) Print
Expand All

Microsoft Security Bulletin MS04-017 - Moderate

Vulnerability in Crystal Reports Web Viewer Could Allow Information Disclosure and Denial of Service (842689)

Published: June 08, 2004 | Updated: June 16, 2004

Version: 1.1

Issued: June 8, 2004
Updated: June 16, 2004
Version: 1.1

Summary

Who should read this document: Customers who use Microsoft® Visual Studio .NET 2003, who use Microsoft Office Outlook 2003 with Business Contact Manager, or who use Microsoft Business Solutions Customer Relationship Management (CRM) 1.2

Impact of Vulnerability:  Information Disclosure and Denial of Service

Maximum Severity Rating: Moderate

Recommendation: Customers should consider applying the security update.

Security Update Replacement: None

Caveats:

  • Customers who use both Visual Studio .NET 2003 and Outlook 2003 with Business Contact Manager, and who have Internet Information Services installed should install the update for both products.
  • The update for the component in Microsoft Business Solutions CRM 1.2 is available on the Business Objects Web site.

Tested Software and Security Update Download Locations:

Affected Software:

Non-Affected Software:

  • All other supported versions of Visual Studio, Outlook, and Microsoft Business Solutions CRM.

Note Outlook 2003 with Business Contact Manager is an add-on to Outlook 2003 that is available on a separate CD, together with Microsoft Office Small Business Edition 2003 and Microsoft Office Professional Edition 2003.

The software in this list has been tested to determine if the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support lifecycle for your product and version, visit the following Microsoft Support Lifecycle Web site.

General Information

Executive Summary:

This update resolves a newly-discovered vulnerability in Crystal Reports and Crystal Enterprise from Business Objects. Microsoft Visual Studio .NET 2003 (all versions) and Outlook 2003 with Business Contact Manager redistribute Crystal Reports and are therefore affected by the vulnerability. Microsoft Business Solutions CRM 1.2 redistributes Crystal Enterprise, which is affected in the same way. The vulnerability is documented in the Vulnerability Details section of this bulletin.

An attacker who successfully exploited the vulnerability could retrieve and delete files through the Crystal Reports and Crystal Enterprise Web viewers on an affected system. The number of files of files that are impacted by this vulnerability would depend on the security context of the affected component that is used by the Crystal Web viewer.

Note Systems can only be vulnerable if they have Internet Information Services (IIS) installed.

Microsoft recommends that customers consider applying the security update.

Severity Ratings and Vulnerability Identifiers:

Vulnerability IdentifiersImpact of VulnerabilityVisual Studio .NET 2003Outlook 2003 with Business Contact ManagerMicrosoft Business Solutions CRM 1.2
Directory Traversal Vulnerability - CAN-2004-0204Information Disclosure
Denial of Service
ModerateModerateModerate

This assessment is based on the types of systems that are affected by the vulnerability, their typical deployment patterns, and the effect that exploiting the vulnerability would have on them.

Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine if this update is required?
No. MBSA does not support Outlook with Business Contact Manager, Visual Studio .NET 2003, or Microsoft Business Solutions CRM 1.2. Microsoft has no plans to develop a scanning tool to determine if a system is vulnerable.

Can I use Systems Management Server (SMS) to determine if this update is required?
Yes. SMS can help detect if there are other programs installed that may have installed a version of the vulnerable component. SMS can search for the existence of the CrystalDecisions.Web.dll file. Update all versions of the CrystalDecisions.Web.dll file that are earlier than version 9.1.9800.9.

Directory Traversal Vulnerability - CAN-2004-0204:

A directory traversal vulnerability exists in Crystal Reports and Crystal Enterprise from Business Objects that could allow Information Disclosure and Denial of Service attacks on an affected system. An attacker who successfully exploited the vulnerability could retrieve and delete files through the Crystal Reports and Crystal Enterprise Web interface on an affected system.

Mitigating Factors for Directory Traversal Vulnerability - CAN-2004-0204:

  • Firewall best practices and standard default firewall configurations can help protect networks from attacks that originate outside the enterprise perimeter. Best practices recommend that systems that are connected to the Internet have a minimal number of ports exposed.
  • Systems can only be vulnerable if they have Internet Information Services (IIS) installed.
  • The attack is only effective against files where the IIS worker process that is hosting the CrystalDecisions.Web.dll file has delete permissions.

Visual Studio .NET 2003

  • By default, the IIS worker process that hosts the component that is used to exploit this vulnerability is configured to run under different security contexts, depending on the operating system and server role. All of these accounts are limited type accounts with limited access to resources that are on the system.
    • On Windows 2000 and Windows XP, the machine\ASPNET account is the default security context.
    • On Windows 2000 domain controllers, the IWAM_MACHINE account is be the default security context.
    • On Windows Server 2003 (IIS Worker Process Isolation Mode), the Network Service account is the default security context.
    • On Windows Server 2003 (IIS5 Compatibility Mode), the machine\ASPNET account is the default security context.
    • On Windows Server 2003 domain controllers, the Network Service account is the default security context.
  • Systems that have Visual Studio .NET 2003 installed are vulnerable only if IIS was installed on the system when Visual Studio was installed, and if IIS is still installed.

Outlook 2003 with Business Contact Manager

  • By default, the IIS worker process that hosts the component that is used to exploit this vulnerability is configured to run under different security contexts, depending on the operating system and server role. All of these accounts are limited type accounts with limited access to resources that are on the system.
  • Systems that have Outlook 2003 with Business Contact Manager installed are vulnerable only if IIS was present on the system when Business Contact Manager was installed.
  • Outlook with Business Contact Manager is not part of a default install of Outlook 2003 but is available on a separate CD, together with Microsoft Office Small Business Edition 2003 and Microsoft Office Professional Edition 2003.

Microsoft Business Solutions CRM 1.2

  • On Microsoft Business Solutions CRM 1.2, only authenticated users can access the Crystal Enterprise Web interface.

Workarounds for Directory Traversal Vulnerability - CAN-2004-0204:

Microsoft has tested the following workarounds. While these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified below.

  • Stop, disable, or remove IIS
    • You can stop IIS by issuing the net stop w3svc command at a command prompt.
    • You can use the IIS Manager to disable or stop IIS.
    • You can use the Add or Remove Programs tool in Control Panel to remove IIS from your system. To find IIS, click Add/Remove Windows Components.

    Impact of Workaround: If you stop w3svc, the system can no longer provide Web content. If you stop or remove IIS, the system can no longer provide Web, FTP, or NTP content. The SMTP service is also unavailable.

  • To stop or pause a Web site by using IIS Manager
    • In IIS Manager, right-click the site that you want to stop or pause, (in this case the crystalreportwebformviewer2 virtual directory); and then click Stop, or Pause.

    Impact of Workaround: The system will no longer provide Crystal Reports through the Crystal Web Interface.

  • To stop or pause a Web site by using a command-line command
    • Click Start, and then click Run, type cmd, and then click OK.
    • At the command prompt, type cscript iisweb.vbs /action "WebSiteName", and then press ENTER. Substitute stop or pause for action. Substitute your actual Web site name (for example "Default Web Site") for WebSiteName.

    Impact of Workaround: The system will no longer provide Crystal Reports through the Crystal Web Interface.

  • Modify the crystalreportwebformviewer2 virtual directory to allow only authenticated and authorized access
    • Use IIS Manager to modify the crystalreportwebformviewer2 virtual directory and make it more restrictive. For example, you can make it allow only members of the Authenticated Users group, and disallow anonymous access.

      Impact of Workaround: Anonymous access to the Crystal Reports Web viewer would no longer be available.

  • Restrict the Access Control List (ACL) on the crystalimagehandler.aspx file to allow access to authenticated and authorized users only
    • IIS supports controlling access to directories and files on a local computer by using all Windows authentication methods. Modify the ACL on the crystalimagehandler.aspx file to be more restrictive. For example, you can make it allow access to only a limited group of authenticated users.
    • Note You must use this workaround in conjunction with the “Modify the crystalreportwebformviewer2 virtual directory to allow only authenticated and authorized access” workaround.

    Impact of Workaround: Only authenticated and authorized users will be able to access your Web site.

FAQ for Directory Traversal Vulnerability - CAN-2004-0204:

What is the scope of the vulnerability?
A directory traversal vulnerability exists in Crystal Reports and Crystal Enterprise from Business Objects that could allow Information Disclosure and Denial of Service attacks on an affected system. An attacker who successfully exploited the vulnerability could retrieve and delete files through the Crystal Reports and Crystal Enterprise Web Viewers on an affected system.

By default, the IIS worker process in Visual Studio .NET 2003 and Outlook 2003 with Business Contact Manager that hosts the component that is used to exploit this vulnerability is configured to run under different security contexts, depending on the operating system and server role. All of these accounts are limited type accounts with limited access to resources that are on the system.

Access to the Crystal Web interface is limited to authenticated users of Microsoft Business Solutions CRM 1.2 through Windows User Group membership. During the initial install, you can pick what security context the CRM server should run under: LocalSYSTEM, Network Service or a domain user. The default is LocalSYSTEM, which would allow authenticated users to attempt this attack against a system under this security context.

What causes the vulnerability?
Crystal Reports and Crystal Enterprise do not correctly validate input before they accept certain HTTP requests.

What are Crystal Reports and Crystal Enterprise?
Crystal Reports and Crystal Enterprise are software offerings from Business Objects. Microsoft redistributes a custom version of Crystal Reports in Visual Studio .NET 2003 and in Outlook 2003 with Business Contact Manager. Microsoft redistributes the Crystal Enterprise 9.0 SDK in Microsoft Business Solutions CRM1.2.

What is Visual Studio .NET 2003?
Visual Studio .NET 2003 is a development tool for building and integrating XML Web services and other applications. It redistributes a custom version of the Crystal Reports embedded report designer, runtime engine, and report viewers.

What is Outlook 2003 with Business Contact Manager?
Outlook 2003 with Business Contact Manager is an Outlook 2003 add-on that can be used to manage business contacts in a single-user contact management solution. It is available on a separate CD, together with Microsoft Office Small Business Edition 2003 and Microsoft Office Professional Edition 2003. It redistributes the Crystal Reports for Visual Studio .NET 2003 runtime.

What is Microsoft Business Solutions CRM 1.2?
By using Microsoft Business Solutions CRM customers can develop customer relationships through lead and opportunity management, incident management, a searchable knowledgebase, and reporting tools. Microsoft Business Solutions CRM 1.2 redistributes the Crystal Enterprise 9.0 SDK.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited the vulnerability could retrieve and delete files through the Crystal Reports and Crystal Enterprise Web interface on an affected system. These files would have to be in a known location, and the security context of the IIS worker process that is running ASP.NET would have to have delete permissions to the file.

Who could exploit the vulnerability?
For Visual Studio .NET 2003 and Outlook 2003 with Business Contact Manager, any anonymous or authenticated user who could access the Crystal Reports Web viewer on the affected system could attempt to exploit this vulnerability.

For CRM 1.2, any authenticated user who could access the Crystal Enterprise Web viewer on the affected system could attempt to exploit this vulnerability.

How could an attacker exploit the vulnerability?
An attacker could exploit the vulnerability by creating a specially crafted HTTP request and attempt to retrieve and delete files through the Crystal Reports and Crystal Enterprise Web viewers on an affected system.

What systems are primarily at risk from the vulnerability?
Systems must have IIS installed and enabled to be at risk in any of the following scenarios.

  • Systems that have Visual Studio .NET 2003 installed are only vulnerable if they had IIS installed when they installed Visual Studio. The affected components are part of a default install of Visual Studio .NET 2003.
  • Systems that have Outlook 2003 with Business Contact Manager are only vulnerable if they had IIS installed when they installed Business Contact Manager.
  • Systems that have Microsoft Business Solutions CRM 1.2 installed are vulnerable. However, only authenticated users can access the Crystal Enterprise Web interface.

I am using the Microsoft Business Solutions CRM 1.2 Sales for Outlook Client. Am I vulnerable?
No. The Microsoft Business Solutions CRM 1.2 Sales for Outlook Client is not affected by this vulnerability.

I have used Visual Studio .NET 2003 to create a custom solution with Crystal Reports, does that solution contain the vulnerability?
Maybe. If you used the Crystal_Managed2003.msm merge module from Visual Studio .NET 2003 in your custom solution, you are likely vulnerable. You should use the workarounds and mitigations that are outlined in this bulletin and see how they apply to your specific custom solution.

I have used the Crystal_Managed2003.msm merge module from Visual Studio .NET 2003 to create a custom solution with Crystal Reports, how do I update my custom solution?
You should visit the Business Objects Web site and see if their security update for solutions that are built by using Visual Studio .NET 2003 will work for you. Because we have not tested this update with your custom solution, neither Microsoft nor Business Objects can guarantee the compatibility of the update with your custom solution. It is recommended that you test the update on a non-production system before you apply the update to systems that are in production.

You should also apply the Visual Studio security update to your development environment and generate a new build of your custom solution for future deployments.

I am using Visual Studio .NET 2003 but I have never had IIS installed. Should I install the update?
Yes. While your system is not vulnerable, any custom solutions that you may create by using the Crystal_Managed2003.msm merge module could be.

I am using Visual Studio .NET 2003, but I do not have IIS installed. Am I vulnerable?
No.

What does the update do?
The update removes the vulnerability by modifying the way that Crystal Reports and Crystal Enterprise validates the HTTP requests.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information indicating that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.

Installation Platforms and Prerequisites:

For information about the specific security update for your platform, click the appropriate link:

Visual Studio .NET 2003

Prerequisites
This security update requires a release version of Visual Studio .NET 2003.

Inclusion in Future Service Packs:
The update for this issue will be included in Visual Studio .NET 2003 Pack 1.

Installation Information

This security update supports the following setup switches:

/? Show installer switches

/I Install (default action)

/U Uninstall (if installed)

/Q Quiet mode

/L:logfile Generate log file

/Ld Log package details.

/Lp Log affected products.

/Lf Log included files.

/XP[:path] Extract MSP.

Deployment Information

To install the security update without any user intervention, use the following command at a command prompt for Visual Studio .NET 2003:

VS7.1- KB 841870-X86.exe /q

Restart Requirement

This security update requires a restart if the file that is being updated is in use when the update is applied to the system.

Removal Information

To remove this update, use the Add or Remove Programs tool in Control Panel.

File Information

The English version of this update has the file attributes (or later) 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.

Visual Studio .NET 2003:

Date Time Version Size File name
-------------------------------------------------------------------------
12-May-04 20:56 9.1.9800.9 151552 CrystalDecisions.Web.dll
13-May-04 19:25 N/A 507392 Crystal_Managed2003.msm

Verifying Update Installation

You may be able to verify the files that this security update has installed by reviewing the following registry keys:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{981DFBF2-F25F-4C20-A2B3-AC64EAA6DD83}

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Visual Studio\7.1\M841870

Outlook 2003 with Business Contact Manager available separately and as a component of Office 2003

Prerequisites and Additional Update Details

This security update requires a release version of Outlook 2003 with Business Contact Manager. In addition:

You must have Microsoft Windows Installer 2.0 installed. Microsoft Windows Server 2003, Windows XP and Microsoft Windows 2000 Service Pack 3 (SP3) include Windows Installer 2.0 or later.

If you have Office 2003 installed, you must be running Microsoft Windows 2000 Service Pack 3 (SP3), you must be running Windows XP, or you must be running a later operating system.

Note Systems that have Outlook 2003 with Business Contact Manager installed are vulnerable only if IIS was installed on the system when Business Contact Manager was installed and if IIS is still installed and enabled.

Inclusion in Future Service Packs:

The fix for this issue will be included in any future service packs for Outlook 2003 with Business Contact Manager.

Restart Requirement

No restart is required.

Removal Information

After you install the update, you cannot remove it. To revert to an installation before the update was installed, you must remove the application, and then install it again from the original CD-ROM.

Client Installation Information

Client Deployment Information

  1. Download the client version of this security update.
  2. Click Save this program to disk, select a folder and then click OK.
  3. Click Save to save the BusinessContactManager-kb842496-fullfile-enu.exe file to disk.
  4. Using Windows Explorer, find to the folder that contains the saved file, double-click the saved file, and then double-click BusinessContactManager-kb842496-fullfile-enu.exe to start the Setup program.

    Follow the instructions that appear on the screen to complete the installation.

  5. Click Yes to accept the License Agreement.
  6. Follow the instructions in the BCM Crystal Hotfix Setup Wizard to complete the installation.
  7. Open Outlook 2003, and then select the Outlook profile that you want to work with Business Contact Manager.

Note If the security is already installed on your computer, you receive the following error message: This update has already been applied or is included in an update that has already been applied.

Client Installation File Information

The English version of this update has the file attributes (or later) 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.

Outlook 2003 with Business Contact Manager:

Date Time Version Size File name
--------------------------------------------------------
20-Oct-03 13:21 N/A 159,213 BCMHelp.chm
13-May-04 14:23 1.00.2002.7 26,112 Common.dll
12-May-04 13:56 9.01.9800.9 151,552 CrystalDecisions.Web.dll
27-Oct-03 15:48 1.00.2002.4 45,568 IrisMS32.dll
27-Oct-03 12:37 1.00.2002.4 876,544 Microsoft.BusinessSolutions.eCRM.OutlookAddIn.dll
27-Oct-03 12:37 1.00.2002.4 823,296 Microsoft.BusinessSolutions.eCRM.OutlookAddIn.CSUtils.dll
27-Oct-03 12:36 1.00.2002.4 397,312 Microsoft.Interop.Mapi.Impl.dll

Verifying Update Installation

Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

  1. Click Start, and then click Search.
  2. In the Search Results window, click All files and folders under Search Companion.
  3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
  4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
  5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate files information table.

Restart Requirement

This security update does not require a restart.

Removal Information

After you install the update, you cannot remove it. To revert to an installation before the update was installed, you must remove the application, and then install it again from the original CD-ROM.

Alternative Installation Information

You can partially automate the installation of this security update using the following information.

Installation Information

You can use the following setup switches to customize the way that the security update files are extracted:

/? Displays the command line options

/Q Specifies quiet mode, or suppresses prompts, when files are being extracted.

/T: <full path> Specifies the target folder for extracting files.

/C Extracts the files without installing them. If /T: path is not specified, you are prompted for a target folder.

/C: <Cmd> Override Install Command defined by author. Specifies the path and name of the Setup .inf or .exe file.

For additional information about the supported setup switches, see Microsoft Knowledge Base Article 197147.

Deployment Information

To update your administrative installation, follow these steps:

  1. Download the client version of this security update.
  2. Click Save this program to disk, select a folder and then click OK.
  3. Click Save to save the BusinessContactManager-kb842496-fullfile-enu.exe file to the disk.
  4. Using Windows Explorer, find the folder that contains the saved file, and then double-click the saved file.
  5. If you are prompted to install the update, click Yes.
  6. Click Yes to accept the License Agreement.
  7. Fill in the Type the location where you want to place the extracted files box, and click OK.
  8. Click Yes when you are prompted to create the folder.
  9. Open a command prompt, and then find the folder that contains the extracted files.
  10. Run the following command to do a silent install of the security update:

    Msiexec /p [path to the MSP file] /q

    For example:

    Msiexec /p C:\temp\BusinessContactManager-FullFile-ENU.msp /q

Customer Relationship Management 1.2

Prerequisites

This security update requires Microsoft Business Solutions CRM 1.2.

Inclusion in Future Service Packs:

The update for this issue will be included in any future service packs for Microsoft Business Solutions CRM 1.2.

Restart Requirement

No restart is required.

Update Availability:

The update for the Business Objects Crystal Enterprise components that are included in Microsoft Business Solutions CRM 1.2 is available on the Business Objects Web site

Other Information

Acknowledgments

Microsoft thanks the following for working with us to help protect customers:

  • Business Objects for working with us on the Directory Traversal Vulnerability (CAN-2004-0204).

Obtaining Other Security Updates:

Updates for other security issues are available from the following locations:

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.
  • Support for Microsoft Business Solutions CRM 1.2 is available through Microsoft Business Solutions. Support options for the Business Objects’ Crystal Enterprise components that are included in Microsoft Business Solutions CRM 1.2 are available at Business Objects' Support Web site.

Security Resources:

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 this security update with Software Update Services, visit the Software 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 to 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, see 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 and the Microsoft Office Detection 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, see 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.

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 (June 8, 2004): Bulletin published
  • V1.1 (June 16, 2004): Added information about restart requirement for the CRM 1.2 update in the Security Update Information section.

Built at 2014-04-18T13:49:36Z-07:00

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2015 Microsoft