Microsoft Security Bulletin MS08-039 - Important
Vulnerabilities in Outlook Web Access for Exchange Server Could Allow Elevation of Privilege (953747)
Published: | Updated:
Version: 1.2
General Information
Executive Summary
This security update resolves two privately reported vulnerabilities in Outlook Web Access (OWA) for Microsoft Exchange Server. An attacker who successfully exploited these vulnerabilities could gain access to an individual OWA client’s session data, allowing elevation of privilege. The attacker could then perform any action the user could perform from within the individual client’s OWA session.
This security update is rated Important for all supported editions of Microsoft Exchange Server 2003 and Microsoft Exchange Server 2007. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The security update addresses the vulnerabilities by modifying the validation of HTTP session data within OWA. For more information about the vulnerabilities, 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 update at the earliest opportunity.
Known Issues. Microsoft Knowledge Base Article 953747 documents the currently known issues that customers may experience when installing this security update.
Affected and Non-Affected Software
The following software 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.
Affected Software
| Software | Maximum Security Impact | Aggregate Severity Rating | Bulletins Replaced by this Update |
|---|---|---|---|
| Microsoft Exchange Server 2003 Service Pack 2 | Elevation of Privilege | Important | None (See Update FAQ for additional details) |
| Microsoft Exchange Server 2007 | Elevation of Privilege | Important | MS07-026 |
| Microsoft Exchange Server 2007 Service Pack 1 | Elevation of Privilege | Important | None (See Update FAQ for additional details) |
Non-Affected Software
| Operating System |
|---|
| Microsoft Exchange Server 2000 Service Pack 3 |
Frequently Asked Questions (FAQ) Related to This Security Update
Where are the file information details?
The file information details can be found in Microsoft Knowledge Base Article 953747.
What are the known issues that customers may experience when installing this security update?
Microsoft Knowledge Base Article 953747 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues.
What is Outlook Web Access (OWA)?
Microsoft Outlook Web Access (OWA) is a service of Exchange Server. By using OWA, a server that is running Exchange Server can also let authorized users read and send mail, manage their calendar, and perform other mail functions from within a browser over the Internet. For more information, see Overview of Outlook Web Access.
The list of files detailed in KB953747 is very large for Exchange 2007. Are all of these files included in this update, and will they be installed on my system?
Yes, the files listed in Microsoft Knowledge Base Article 953747 are all included in the update for the various versions of Exchange 2007 and will be installed with the update. As detailed below, the Exchange 2007 servicing model is cumulative, so that each update contains all previously released fixes and files from all previous update rollups.
What is the difference between the servicing models of Microsoft Exchange Server 2007 and Microsoft Exchange Server 2003, and how does the difference impact the updates in this security bulletin?
With the release of Microsoft Exchange 2007, Microsoft Exchange has moved to a new servicing model based on customer feedback and consistency with other Microsoft product servicing models. Exchange 2007 updates are cumulative at both the offered update level and at the individual file level, while Exchange Server 2003 updates are cumulative at the file level only.
For a more detailed explanation of the Microsoft Exchange servicing model, please see the Microsoft Exchange Server 2007 product documentation. For questions regarding the new Exchange servicing model, please contact Microsoft Product Support Services.
Why does this update address several reported security vulnerabilities?
This update contains support for several vulnerabilities because the modifications that are required to address these issues are located in related files. Instead of having to install several updates that are almost the same, customers need to install this update only.
Does this update contain any additional security related changes?
Yes. In addition to the changes that are described in the Vulnerability Details section of this bulletin, this update includes additional security changes. For a complete list of files and additional changes included in this update, please see Microsoft Knowledge Base Article 953747.
Does this update contain any non-security related changes?
Yes. In addition to the changes that are described in the Vulnerability Details section of this bulletin, this update includes non-security changes due to the cumulative nature of the Exchange servicing model. For a complete list of files and additional non-security related changes included in this update, please see Microsoft Knowledge Base Article 953747.
As with all updates, Microsoft encourages customers to perform testing of critical line-of-business applications and infrastructure that could be affected by this update prior to deployment.
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 Microsoft Support Lifecycle. For more information about the extended security update support period for these software versions or editions, visit Microsoft Product Support Services.
Customers who require custom support for older releases 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 Microsoft Worldwide Information, 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 | Outlook Web Access for Exchange Server Data Validation Cross-Site Scripting Vulnerability - CVE-2008-2247 | Outlook Web Access for Exchange Server Parsing Cross-Site Scripting Vulnerability - CVE-2008-2248 | Aggregate Severity Rating |
|---|---|---|---|
| Microsoft Exchange Server 2003 Service Pack 2 | Important Elevation of Privilege | Not applicable | Important |
| Microsoft Exchange Server 2007 | Not applicable | Important Elevation of Privilege | Important |
| Microsoft Exchange Server 2007 Service Pack 1 | Not applicable | Important Elevation of Privilege | Important |
Outlook Web Access for Exchange Server Data Validation Cross-Site Scripting Vulnerability - CVE-2008-2247
This is a cross-site scripting vulnerability in the affected versions of Outlook Web Access (OWA) for Exchange Server. Exploitation of the vulnerability could lead to elevation of privilege on individual OWA clients connecting to Outlook Web Access for Exchange Server. To exploit the vulnerability, an attacker would have to convince a user to open a specially crafted e-mail that would run malicious script from within an individual OWA client. If the malicious script is executed, the script would run in the security context of the user’s OWA session and could perform any action the user could perform such as reading, sending, and deleting e-mail as the logged-on user.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-2247.
Mitigating Factors for Outlook Web Access for Exchange Server Data Validation Cross-Site Scripting Vulnerability - CVE-2008-2247
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 factors may be helpful in your situation:
- OWA Premium is not impacted by this vulnerability. OWA Premium is the OWA interface that provides additional functionality from within OWA, such as the preview pane, spell checking, having the folder list and inbox open at the same time, and additional features such as rules. For additional information on Outlook Web Access Light and Outlook Web Access Premium and the different features between the two versions, see Client Features in Outlook Web Access.
Note OWA Premium is only available when accessing OWA with Internet Explorer in Microsoft Windows. For additional information on which versions of Internet Explorer support OWA Premium, see Educating Information Workers About Outlook Web Access.
Workarounds for Outlook Web Access for Exchange Server Data Validation Cross-Site Scripting Vulnerability - CVE-2008-2247
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:
Microsoft has not identified any workarounds for this vulnerability.
FAQ for Outlook Web Access for Exchange Server Data Validation Cross-Site Scripting Vulnerability - CVE-2008-2247
What is the scope of the vulnerability?
This is a cross-site scripting vulnerability in Outlook Web Access (OWA) for Exchange Server. Exploitation of the vulnerability could allow an attacker to gain access to an individual client’s OWA session data allowing elevation of privilege. The attacker could then perform any action the user could perform from within OWA such as reading, sending, and deleting e-mail as the logged-on user.
What causes the vulnerability?
The vulnerability is a result of Outlook Web Access for Exchange Server not sufficiently validating e-mail fields when opening mail from within an individual client’s OWA session.
What is cross-site scripting?
Cross-site scripting (XSS) is a security vulnerability that could enable an attacker to "inject" code into a user's session with a Web site. Unlike most security vulnerabilities, XSS does not apply to any single vendor's products–instead, it can affect any software that generates HTML and that does not follow defensive programming practices.
How does cross-site scripting work?
Web pages contain text and HTML markup. Text and HTML markup are generated by the server and are interpreted by the client. Servers that generate static pages have full control over the way that the client interprets the pages that the server sends. However, servers that generate dynamic pages do not have control over the way that the client interprets the server’s output. If untrusted content is introduced into a dynamic page, neither the server nor the client has sufficient information to recognize that this action has occurred and to take protective measures.
How could an attacker exploit the vulnerability?
An attacker could attempt to exploit this vulnerability by convincing a user to open a specially crafted e-mail message via an individual client’s OWA session. The message could then cause malicious script to run on the individual client’s system in the context of the user’s OWA session.
What might an attacker use the vulnerability to do?
An attacker could use this vulnerability in Outlook Web Access for Exchange Server to run malicious script on an individual user’s system in the context of the user’s OWA session. The attacker could then perform OWA actions as the logged-on user, such as reading, sending, or deleting e-mail as the logged-on user.
What systems are primarily at risk from the vulnerability?
Systems where Outlook Web Access (OWA) for Exchange Server is installed are the systems where the attack can occur. However, individual OWA clients connecting to the Outlook Web Access for Exchange Server are primarily at risk for elevation of privilege.
What does the update do?
This update addresses the vulnerability by sufficiently validating e-mail fields when opening mails from within OWA.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued. This security bulletin addresses the privately disclosed vulnerability as well as additional issues discovered through internal investigations.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate 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.
Outlook Web Access for Exchange Server HTML Parsing Cross-Site Scripting Vulnerability - CVE-2008-2248
This is a cross-site scripting vulnerability in the affected versions of Outlook Web Access (OWA) for Exchange Server. Exploitation of the vulnerability could lead to elevation of privilege on individual OWA clients connecting to Outlook Web Access for Exchange Server. To exploit the vulnerability an attacker would have to convince a user to open a specially crafted e-mail that would run malicious script from within an individual OWA client. The script would run in the security context of the user’s OWA session and could perform any action the user could perform, such as reading, sending, and deleting e-mail as the logged-on user.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-2248.
Mitigating Factors for Outlook Web Access for Exchange Server HTML Parsing Cross-Site Scripting Vulnerability - CVE-2008-2248
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 factors may be helpful in your situation:
- OWA Premium is not impacted by this vulnerability. OWA Premium is the OWA interface that provides additional functionality from within OWA, such as the preview pane, spell checking, having the folder list and inbox open at the same time, and additional features such as rules. For additional information on Outlook Web Access Light and Outlook Web Access Premium and the different features between the two versions, see Client Features in Outlook Web Access.
Note OWA Premium is only available when accessing OWA with Internet Explorer in Microsoft Windows. For additional information on which versions of Internet Explorer support OWA Premium, see Educating Information Workers About Outlook Web Access.
Workarounds for Outlook Web Access for Exchange Server HTML Parsing Cross-Site Scripting Vulnerability - CVE-2008-2248
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:
Microsoft has not identified any workarounds for this vulnerability.
FAQ for Outlook Web Access for Exchange Server HTML Parsing Cross-Site Scripting Vulnerability - CVE-2008-2248
What is the scope of the vulnerability?
This is a cross-site scripting vulnerability in Outlook Web Access (OWA) for Exchange Server. Exploitation of the vulnerability could allow an attacker to gain access to an individual client’s OWA session data and effect an elevation of privilege. The attacker could then perform any action the user could perform from within OWA such as reading, sending, and deleting e-mail as the logged on user.
What causes the vulnerability?
The vulnerability is a result of Outlook Web Access (OWA) for Exchange Server not sufficiently validating HTML when rendering e-mail from within an individual OWA client session.
What is cross-site scripting?
Cross-site scripting (XSS) is a security vulnerability that could enable an attacker to "inject" code into a user's session with a Web site. Unlike most security vulnerabilities, XSS does not apply to any single vendor's products–instead, it can affect any software that generates HTML and that does not follow defensive programming practices.
How does cross-site scripting work?
Web pages contain text and HTML markup. Text and HTML markup are generated by the server and are interpreted by the client. Servers that generate static pages have full control over the way that the client interprets the pages that the server sends. However, servers that generate dynamic pages do not have control over the way that the client interprets the servers’ output. If untrusted content is introduced into a dynamic page, neither the server nor the client has sufficient information to recognize that this action has occurred and to take protective measures.
How could an attacker exploit the vulnerability?
An attacker could attempt to exploit this vulnerability by convincing a user to open a specially crafted e-mail message via the user’s OWA session. The message could then cause malicious script to run on the individual client’s system in the context of the user’s OWA session.
What might an attacker use the vulnerability to do?
An attacker could use this vulnerability in Outlook Web Access for Exchange Server to run remote code on an individual client’s system in the context of the user’s OWA session and perform OWA actions as the logged-on user, such as reading, sending, or deleting e-mail as the logged-on user.
What systems are primarily at risk from the vulnerability?
Systems where Outlook Web Access (OWA) for Exchange Server is installed are the systems where the attack can occur. However, individual OWA clients connecting to the Outlook Web Access (OWA) for Exchange Server are primarily at risk for elevation of privilege.
What does the update do?
This update addresses the vulnerability by modifying the way that Outlook Web Access for Exchange Server validates HTML when rendering e-mails from within an individual OWA client session.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued. This security bulletin addresses the privately disclosed vulnerability as well as additional issues discovered through internal investigations.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate 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.
Update Information
Detection and Deployment Tools and Guidance
Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems 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 from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update."
Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, “MS07-036”), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ.
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), and the Extended Security Update Inventory Tool. For more information, see Microsoft Knowledge Base Article 910723.
Microsoft Baseline Security Analyzer
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.
The following table provides the MBSA detection summary for this security update.
| Software | MBSA 2.1 |
|---|---|
| Microsoft Exchange Server 2003 Service Pack 2 | Yes |
| Microsoft Exchange Server 2007 | Yes |
| Microsoft Exchange Server 2007 Service Pack 1 | Yes |
For more information about MBSA 2.1, see MBSA 2.1 Frequently Asked Questions.
Windows Server Update Services
By using Windows Server Update Services (WSUS), administrators can deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003 and later, and SQL Server 2000 and later. 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 with SUSFP | SMS 2003 with ITMU | SCCM 2007 |
|---|---|---|---|---|
| Microsoft Exchange Server 2003 Service Pack 2 | Yes | Yes | Yes | Yes |
| Microsoft Exchange Server 2007 | No | No | Yes | Yes |
| Microsoft Exchange Server 2007 Service Pack 1 | No | No | Yes | Yes |
For SMS 2.0 and SMS 2003, the SMS SUS Feature Pack (SUSFP), which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. See also Downloads for Systems Management Server 2.0.
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, see SMS 2003 Inventory Tool for Microsoft Updates. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications. For more information about the Office Inventory Tool and other scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.
System Center Configuration Manager (SCCM) 2007 uses WSUS 3.0 for detection of updates. For more information about SCCM 2007 Software Update Management, visit System Center Configuration Manager 2007.
For more information about SMS, visit the SMS Web site.
For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.
Update Compatibility Evaluator and Application Compatibility Toolkit
Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit 5.0.
The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.
Security Update Deployment
Affected Software
For information about the specific security update for your affected software, click the appropriate link:
Microsoft Exchange Server 2003 (all editions)
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 | Microsoft Exchange Server 2003 Service Pack 2: Exchange2003-kb950159-x86-enu /quiet |
| Installing without restarting | Microsoft Exchange Server 2003 Service Pack 2: Exchange2003-kb950159-x86-enu /norestart |
| Update log file | kb950159.log |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | No, this update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if 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 your computer, see Microsoft Knowledge Base Article 887012. |
| HotPatching | Not applicable |
| Removal Information | Microsoft Exchange Server 2003 Service Pack 2: Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB950159$\Spuninst folder |
| File Information | See Microsoft Knowledge Base Article 953747 |
| Registry Key Verification | Microsoft Exchange Server 2003 Service Pack 2: HKEY_LOCAl_MACHINE\SOFTWARE\Microsoft\Updates\Exchange Server 2003\SP3\KB950159\Filelist |
Deployment Information
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft Exchange hotfix.
For more information about the installer, visit the Microsoft TechNet Web site.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed. |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Displays a dialog box prompting the local user to allow a restart. |
| Special Options | |
| /overwriteoem | Overwrites OEM files without prompting. |
| /nobackup | Does not back up files needed for uninstall. |
| /forceappsclose | Forces other programs to close when the computer shuts down. |
| /log:path | Allows the redirection of installation log files. |
| /extract[:path] | Extracts files without starting the Setup program. |
| /ER | Enables extended error reporting. |
| /verbose | Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Removing the Update
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed. |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Displays a dialog box prompting the local user to allow a restart. |
| Special Options | |
| /forceappsclose | Forces other programs to close when the computer shuts down. |
| /log:path | Allows the redirection of installation log 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.
Microsoft Exchange Server 2007 (all editions)
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 will be included in a future service pack or update rollup |
| Deployment | |
| Installing without user intervention | Microsoft Exchange Server 2007: Exchange2007-kb953469-x64-en /quiet Exchange2007-kb953469-x86-en /quiet Microsoft Exchange Server 2007 Service Pack 1: |
| Installing without restarting | Microsoft Exchange Server 2007: Exchange2007-kb953469-x64-en /norestart Exchange2007-kb953469-x86-en /norestart Microsoft Exchange Server 2007 Service Pack 1: |
| Update log file | For Microsoft Exchange Server 2007: KB953469.log For Microsoft Exchange Server 2007 Service Pack 1: |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | No, this update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if 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 your computer, see Microsoft Knowledge Base Article 887012. |
| HotPatching | Not applicable |
| Removal Information | To remove this update, use Add or Remove Programs in Control Panel. |
| File Information | See Microsoft Knowledge Base Article 953747 |
| Registry Key Verification | For Microsoft Exchange Server 2007: HKEY_LOCAl_MACHINE\SOFTWARE\Microsoft\Updates\Exchange 2007\SP1\KB953469\ For Microsoft Exchange Server 2007 Service Pack 1: |
Deployment Information
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
For more information about the installer, visit the Microsoft TechNet Web site.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /q[n|b|r|f] | Sets user interface level. n - No user interaction b - Basic user interaction r - Reduced user interaction f - Full user interaction (default) |
| Restart Options | |
| /norestart | Does not restart when installation has completed. |
| /forcerestart | Restarts the computer after installation and forces other applications to close at shutdown without saving open files first. |
| /promptrestart | Display a dialog box prompting the local user to allow a restart. |
| 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> |
Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
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
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
- Michael Jordan of Context Information Security for reporting the OWA Data Validation Cross-Site Scripting Vulnerability (CVE-2008-2247) and the OWA Parsing Cross-Site Scripting Vulnerability (CVE-2008-2248)
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 (July 8, 2008): Bulletin published.
- V1.1 (July 9, 2008): Changed the information reference link for OWA Premium in the Mitigating Factors sections for both vulnerabilities.
- V1.2 (July 16, 2008): Added Microsoft Exchange Server 2000 Service Pack 3 as non-affected software. Also provided links to additional information on Outlook Web Access Light and Outlook Web Access Premium in the Mitigating Factors sections. Finally, updated the applicable software under the “Windows Server Update Services” heading in the section, Detection and Deployment Tools and Guidance.