Article ID: 301361 - View products that this article applies to.
This article was previously published under Q301361
This article has been archived. It is offered "as is" and will no longer be updated.
For additional information about a similar problem that may occur in Exchange 2000 Server, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/299535/EN-US/ )XGEN: Incorrect Attachment Processing in Exchange 2000 Outlook Web Access Can Run Script
Microsoft Outlook Web Access (OWA) is a service of Exchange Server 5.5 and Exchange 2000 Server that a user can use to gain access to an Exchange mailbox by using a Web browser. However, vulnerability exists in the interaction between OWA and Microsoft Internet Explorer for message attachments. If an attachment contains Hypertext Markup Language (HTML) code that includes script, the script is run when the user opens the attachment, regardless of the attachment type. Because OWA requires that scripting be enabled in the zone where the OWA server is located, this script can take action against the user's Exchange mailbox.
An attacker might use this vulnerability to construct an attachment that contains malicious script code. The attacker can then send the attachment in a message to a user. If the user opens the attachment in OWA, the script runs and can take action against the user’s mailbox as if the script is the user, including, under certain circumstances, manipulation of messages or folders.
The following are mitigating factors:
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that you determine are at risk of attack. Evaluate your computer's physical accessibility, network and Internet connectivity, and other factors to determine the degree of risk to your computer. See the associated Microsoft Security Bulletin
(http://www.microsoft.com/technet/security/bulletin/MS01-030.mspx)to help determine the degree of risk. This fix may receive additional testing. If your computer is sufficiently at risk, Microsoft recommends that you apply this fix now. Otherwise, wait for the next Microsoft Exchange Server 5.5 service pack that contains this fix.
To resolve this problem immediately, download the fix by following the instructions later in this article or contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMSNOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The following files are available for download from the Microsoft Download Center:
Release Date: June 8, 2001
Download Q301361i386.exe now
Collapse this imageExpand this image
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.
(https://support.microsoft.com/kb/119591/EN-US/ )How to Obtain Microsoft Support Files from Online Services
The English version of this fix should have the following file attributes or later:
Collapse this tableExpand this table
Microsoft has confirmed that this problem may cause a degree of security vulnerability in Microsoft Exchange Server version 5.5.
For more information about this security vulnerability, see the following Microsoft Web site:
Article ID: 301361 - Last Review: October 24, 2013 - Revision: 5.2