In this article

Microsoft Security Bulletin MS11-002 - Critical

General Information

Executive Summary

This security update resolves two privately reported vulnerabilities in Microsoft Data Access Components. The vulnerabilities could allow remote code execution if a user views a specially crafted Web page. 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.

This security update is rated Critical for all supported editions of Windows XP, Windows Vista, and Windows 7, and Important for all supported editions of Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerabilities by ensuring that MDAC correctly validates string length and memory allocation. 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. The majority of customers have automatic updating enabled and will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.

For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update immediately using update management software, or by checking for updates using the Microsoft Update service.

See also the section, Detection and Deployment Tools and Guidance, later in this bulletin.

Known Issues. None

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.

**\*Server Core installation affected.** This update applies, with the same severity rating, to supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, whether or not installed using the Server Core installation option. For more information on this installation option, see the TechNet articles, [Managing a Server Core Installation](http://technet.microsoft.com/en-us/library/ee441255(ws.10).aspx) and [Servicing a Server Core Installation](http://technet.microsoft.com/en-us/library/ff698994(ws.10).aspx). Note that the Server Core installation option does not apply to certain editions of Windows Server 2008 and Windows Server 2008 R2; see [Compare Server Core Installation Options](http://www.microsoft.com/windowsserver2008/en/us/compare-core-installation.aspx).
Frequently Asked Questions (FAQ) Related to This Security Update
----------------------------------------------------------------
**Where are the file information details?**
Refer to the reference tables in the **Security Update Deployment** section for the location of the file information details.
**How are the Windows 7 Service Pack 1 Beta and Windows Server 2008 R2 Service Pack 1 Beta releases affected by this vulnerability?**
Windows 7 Service Pack 1 Beta and Windows Server 2008 R2 Service Pack 1 Beta are affected by the vulnerabilities described in this bulletin. Customers running these beta releases are encouraged to download and apply the update to their systems. Security updates are available from [Microsoft Update](http://go.microsoft.com/fwlink/?linkid=40747) and [Windows Update](http://update.microsoft.com/). The security update is also available for download from the [Microsoft Download Center](http://go.microsoft.com/fwlink/?linkid=21129).
**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. For more information about the product lifecycle, visit the [Microsoft Support Lifecycle](http://go.microsoft.com/fwlink/?linkid=21742) Web site.
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. To determine the support lifecycle for your software release, see [Select a Product for Lifecycle Information](http://go.microsoft.com/fwlink/?linkid=169555). For more information about service packs for these software releases, see [Lifecycle Supported Service Packs](http://go.microsoft.com/fwlink/?linkid=89213).
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](http://go.microsoft.com/fwlink/?linkid=33329) Web site, select the country in the Contact Information list, 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 [Microsoft Support Lifecycle Policy FAQ](http://go.microsoft.com/fwlink/?linkid=169557).
### Vulnerability Information
Severity Ratings and Vulnerability Identifiers
----------------------------------------------
The following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin's release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the [January bulletin summary](http://technet.microsoft.com/security/bulletin/ms11-jan). For more information, see [Microsoft Exploitability Index](http://technet.microsoft.com/en-us/security/cc998259.aspx).

**\*Server Core installation affected.** This update applies, with the same severity rating, to supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, whether or not installed using the Server Core installation option. For more information on this installation option, see the TechNet articles, [Managing a Server Core Installation](http://technet.microsoft.com/en-us/library/ee441255(ws.10).aspx) and [Servicing a Server Core Installation](http://technet.microsoft.com/en-us/library/ff698994(ws.10).aspx). Note that the Server Core installation option does not apply to certain editions of Windows Server 2008 and Windows Server 2008 R2; see [Compare Server Core Installation Options](http://www.microsoft.com/windowsserver2008/en/us/compare-core-installation.aspx).
DSN Overflow Vulnerability - CVE-2011-0026
------------------------------------------
A remote code execution vulnerability exists in the way that Microsoft Data Access Components validates third-party API usage. This vulnerability could allow code execution if a user visited a specially crafted Web page. 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.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see [CVE-2011-0026](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2011-0026).
#### Mitigating Factors for DSN Overflow Vulnerability - CVE-2011-0026
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:
- This vulnerability cannot be exploited in the default Windows configuration. In order to be vulnerable to the issue, a third-party application that uses specific [Open Database Connectivity](http://support.microsoft.com/kb/110093) (ODBC) APIs in a vulnerable manner must be installed on the system.
#### Workarounds for DSN Overflow Vulnerability - CVE-2011-0026
Microsoft has not identified any workarounds for this vulnerability.
#### FAQ for DSN Overflow Vulnerability - CVE-2011-0026
**What is the scope of the vulnerability?**
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on 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.
**Could this vulnerability be exploited remotely?**
There are no Microsoft applications that expose this vulnerability. However, third-party applications may allow access to [Open Database Connectivity](http://support.microsoft.com/kb/110093) (ODBC) APIs from untrusted sources and thus expose this vulnerability remotely. In such a scenario, exploitation of this vulnerability could allow an anonymous user to execute code with full administrative privileges.
**What causes the vulnerability?**
A buffer overflow exists in the Data Source Name (DSN) argument of an [Open Database Connectivity](http://support.microsoft.com/kb/110093) (ODBC) API that may be used by third-party applications.
**What is Microsoft Data Access Components?**
[Microsoft Data Access Components](http://msdn.microsoft.com/en-us/library/aa968814(v=vs.85).aspx) (MDAC) is a collection of components that make it easy for programs to access databases and then to manipulate the data within them. Modern databases may take a variety of forms (for example, SQL Server databases, Microsoft Access databases, and XML files) and may be housed in a variety of locations (for example, on the local system or on a remote database server). MDAC provides a consolidated set of functions for working with different kinds of data sources in a consistent manner. Starting with Windows Vista, MDAC is referred to as Windows Data Access Components (WDAC).
**What might an attacker use the vulnerability to do?**
An attacker who successfully exploited this vulnerability could gain the same user rights as a logged-on user. If the 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.
**How could an attacker exploit the vulnerability?**
An attacker could host a specially crafted Web site that is designed to exploit this vulnerability through a Web browser and then convince a user to view the Web site. The attacker could also take advantage of compromised Web sites and Web sites that accept or host user-provided content or advertisements. These Web sites could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or in an Instant Messenger message that takes users to the attacker's Web site. It could also be possible to display specially crafted Web content by using banner advertisements or by using other methods to deliver Web content to affected systems.
**What systems are primarily at risk from the vulnerability?**
Workstations and terminal servers 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 addresses this vulnerability by ensuring that MDAC correctly validates string length within MDAC APIs.
**When this security bulletin was issued, had this vulnerability been publicly disclosed?**
No. Microsoft received information about this vulnerability through coordinated vulnerability disclosure.
**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 when this security bulletin was originally issued.
ADO Record Memory Vulnerability - CVE-2011-0027
-----------------------------------------------
A remote code execution vulnerability exists in the way that Microsoft Data Access Components validates memory allocation. This vulnerability could allow code execution if a user visited a specially crafted Web page. 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.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see [CVE-2011-0027](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2011-0027).
#### Mitigating Factors for ADO Record Memory Vulnerability - CVE-2011-0027
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:
- In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's 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.
- By default, all supported versions of Microsoft Outlook, Microsoft Outlook Express, and Windows Mail open HTML e-mail messages in the Restricted sites zone, which disables script and ActiveX controls, removing the risk of an attacker being able to use this vulnerability to execute malicious code. If a user clicks a link in an e-mail message, the user could still be vulnerable to exploitation of this vulnerability through the Web-based attack scenario.
- By default, Internet Explorer on Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2 runs in a restricted mode that is known as [Enhanced Security Configuration](http://technet.microsoft.com/en-us/library/dd883248(ws.10).aspx). This mode mitigates this vulnerability. See the FAQ section of this security update for more information about Internet Explorer Enhanced Security Configuration.
#### Workarounds for ADO Record Memory Vulnerability - CVE-2011-0027
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:
- **Set Internet and Local intranet security zone settings to "High" to block ActiveX Controls and Active Scripting in these zones**
You can help protect against exploitation of this vulnerability by changing your settings for the Internet security zone to block ActiveX controls and Active Scripting. You can do this by setting your browser security to High.
To raise the browsing security level in Internet Explorer, follow these steps:
1. On the Internet Explorer **Tools** menu, click **Internet Options**.
2. In the **Internet Options** dialog box, click the **Security** tab, and then click the **Internet** icon.
3. Under **Security level for this zone**, move the slider to **High**. This sets the security level for all Web sites you visit to High.
**Note** If no slider is visible, click **Default Level**, and then move the slider to **High**.
**Note** Setting the level to High may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly even with the security setting set to High.
**Impact of workaround.** There are side effects to blocking ActiveX Controls and Active Scripting. Many Web sites that are on the Internet or on an intranet use ActiveX or Active Scripting to provide additional functionality. For example, an online e-commerce site or banking site may use ActiveX Controls to provide menus, ordering forms, or even account statements. Blocking ActiveX Controls or Active Scripting is a global setting that affects all Internet and intranet sites. If you do not want to block ActiveX Controls or Active Scripting for such sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone".
**Add sites that you trust to the Internet Explorer Trusted sites zone**
After you set Internet Explorer to block ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect yourself from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.
To do this, follow these steps:
1. In Internet Explorer, click **Tools**, click **Internet Options**, and then click the **Security** tab.
2. In the **Select a Web content zone to specify its current security settings** box, click **Trusted Sites**, and then click **Sites**.
3. If you want to add sites that do not require an encrypted channel, click to clear the **Require server verification (https:) for all sites in this zone** check box.
4. In the **Add this Web site to the zone** box, type the URL of a site that you trust, and then click **Add**.
5. Repeat these steps for each site that you want to add to the zone.
6. Click **OK** two times to accept the changes and return to Internet Explorer.
**Note** Add any sites that you trust not to take malicious action on your system. Two in particular that you may want to add are **\*.windowsupdate.microsoft.com** and **\*.update.microsoft.com**. These are the sites that will host the update, and it requires an ActiveX Control to install the update.
- **Configure Internet Explorer to prompt before running Active Scripting or to disable Active Scripting in the Internet and Local intranet security zone**
You can help protect against exploitation of this vulnerability by changing your settings to prompt before running Active Scripting or to disable Active Scripting in the Internet and Local intranet security zone. To do this, follow these steps:
1. In Internet Explorer, click **Internet Options** on the **Tools** menu.
2. Click the **Security** tab.
3. Click **Internet**, and then click **Custom Level**.
4. Under **Settings**, in the **Scripting** section, under **Active Scripting**, click **Prompt** or **Disable**, and then click **OK**.
5. Click **Local intranet**, and then click **Custom Level**.
6. Under **Settings**, in the **Scripting** section, under **Active Scripting**, click **Prompt** or **Disable**, and then click **OK**.
7. Click **OK** two times to return to Internet Explorer.
**Note** Disabling Active Scripting in the Internet and Local intranet security zones may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly.
**Impact of workaround.** There are side effects to prompting before running Active Scripting. Many Web sites that are on the Internet or on an intranet use Active Scripting to provide additional functionality. For example, an online e-commerce site or banking site may use Active Scripting to provide menus, ordering forms, or even account statements. Prompting before running Active Scripting is a global setting that affects all Internet and intranet sites. You will be prompted frequently when you enable this workaround. For each prompt, if you feel you trust the site that you are visiting, click **Yes** to run Active Scripting. If you do not want to be prompted for all these sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone".
**Add sites that you trust to the Internet Explorer Trusted sites zone**
After you set Internet Explorer to require a prompt before it runs ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect you from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.
To do this, follow these steps:
1. In Internet Explorer, click **Tools**, click **Internet Options**, and then click the **Security** tab.
2. In the **Select a Web content zone to specify its current security settings** box, click **Trusted Sites**, and then click **Sites**.
3. If you want to add sites that do not require an encrypted channel, click to clear the **Require server verification (https:) for all sites in this zone** check box.
4. In the **Add this Web site to the zone** box, type the URL of a site that you trust, and then click **Add**.
5. Repeat these steps for each site that you want to add to the zone.
6. Click **OK** two times to accept the changes and return to Internet Explorer.
**Note** Add any sites that you trust not to take malicious action on your system. Two in particular that you may want to add are **\*.windowsupdate.microsoft.com** and **\*.update.microsoft.com**. These are the sites that will host the update, and it requires an ActiveX Control to install the update.
- **Disable the ActiveX Data Objects (ADO) DLL**
Run the following commands from a command prompt as an administrator:
**For 32-bit editions of Windows XP and Windows Server 2003:**
`cacls "%ProgramFiles%\Common Files\System\ado\msado15.dll" /E /P everyone:N`
**For 64-bit editions of Windows XP and Windows Server 2003:**
`cacls "%ProgramFiles(86)%\Common Files\System\ado\msado15.dll" /E /P everyone:Ncacls "%ProgramFiles%\Common Files\System\ado\msado15.dll" /E /P everyone:N`
**For 32- bit editions of Windows Vista, Windows Server 2008, and Windows 7:**
```
takeown /f "%ProgramFiles%\Common Files\System\ado\msado15.dll"
icacls "%ProgramFiles%\Common Files\System\ado\msado15.dll" /save %TEMP%\MSADO15_ACL.TXT
icacls "%ProgramFiles%\Common Files\System\ado\msado15.dll" /deny everyone(F)
```
**For 64-bit editions of Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2:**
```
takeown /f "%ProgramFiles(86)%\Common Files\System\ado\msado15.dll"
icacls "%ProgramFiles(86)%\Common Files\System\ado\msado15.dll" /save %TEMP%\MSADO15_ACL.TXT
icacls "%ProgramFiles(86)%\Common Files\System\ado\msado15.dll" /deny everyone (F)

FAQ for ADO Record Memory Vulnerability - CVE-2011-0027

What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on 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.

What causes the vulnerability?
MDAC does not correctly allocate memory when handling internal data structures.

What is Microsoft Data Access Components?Microsoft Data Access Components (MDAC) is a collection of components that make it easy for programs to access databases and then to manipulate the data within them. Modern databases may take a variety of forms (for example, SQL Server databases, Microsoft Access databases, and XML files) and may be housed in a variety of locations (for example, on the local system or on a remote database server). MDAC provides a consolidated set of functions for working with different kinds of data sources in a consistent manner. Starting with Windows Vista, MDAC is referred to as Windows Data Access Components (WDAC).

ActiveX Data Objects (ADO), part of MDAC, is a language-neutral object model that exposes data raised by an underlying OLE DB Provider.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could gain the same user rights as a logged-on user. If the 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.

How could an attacker exploit the vulnerability?
An attacker could host a specially crafted Web site that is designed to exploit this vulnerability through Internet Explorer and then convince a user to view the Web site. The attacker could also take advantage of compromised Web sites and Web sites that accept or host user-provided content or advertisements. These Web sites could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or in an Instant Messenger message that takes users to the attacker's Web site. It could also be possible to display specially crafted Web content by using banner advertisements or by using other methods to deliver Web content to affected systems.

What systems are primarily at risk from the vulnerability?
This vulnerability requires that a user be logged on and visiting a Web site for any malicious action to occur. Therefore, any systems where Internet Explorer is used frequently, such as workstations or terminal servers, are at the most risk from this vulnerability.

I am running Internet Explorer for Windows Server 2003, Windows Server 2008, or Windows Server 2008 R2. Does this mitigate this vulnerability?
Yes. By default, Internet Explorer on Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2 runs in a restricted mode that is known as Enhanced Security Configuration. Enhanced Security Configuration is a group of preconfigured settings in Internet Explorer that can reduce the likelihood of a user or administrator downloading and running specially crafted Web content on a server. This is a mitigating factor for Web sites that you have not added to the Internet Explorer Trusted sites zone.

What does the update do?
The update addresses this vulnerability by ensuring that MDAC correctly validates memory allocation.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through coordinated vulnerability disclosure.

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 when this security bulletin was originally issued.

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 provides detection and deployment guidance for security updates. This guidance contains recommendations and information that can help IT professionals understand how to use various tools for detection and deployment of security updates. For more information, see Microsoft Knowledge Base Article 961747.

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.

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.

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:

Windows XP (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

In some cases, this update does not require a restart. If the 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, see Microsoft Knowledge Base Article 887012.

HotPatching

Not applicable

Removal Information

For Microsoft Data Access Components 2.8 Service Pack 1 on Windows XP Service Pack 3:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB2419632$\Spuninst folder

For Microsoft Data Access Components 2.8 Service Pack 2 on Windows XP Professional x64 Edition Service Pack 2:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB2419635$\Spuninst folder

Note For supported versions of Windows XP Professional x64 Edition, this security update is the same as supported versions of the Windows Server 2003 x64 Edition security update.

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.

If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.

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.

**/integrate:path**

Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.

**/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](http://support.microsoft.com/kb/262841).

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe 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.

Windows 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 will be included in a future service pack or update rollup

In some cases, this update does not require a restart. If the 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, see Microsoft Knowledge Base Article 887012.

#### 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.
If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see [Microsoft Knowledge Base Article 824994](http://support.microsoft.com/kb/824994).
For more information about the installer, see [Microsoft Knowledge Base Article 832475](http://support.microsoft.com/kb/832475).
For more information about the terminology that appears in this bulletin, such as *hotfix*, see [Microsoft Knowledge Base Article 824684](http://support.microsoft.com/kb/824684).
This security update supports the following setup switches.

Supported Security Update Installation 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.

**/integrate:path**

Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.

**/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 many of 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](http://support.microsoft.com/kb/262841).

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe 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.

Windows Vista (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

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.

HotPatching

Not applicable.

Removal Information

WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.

Note A registry key does not exist to validate the presence of this update.

#### 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 terminology that appears in this bulletin, such as *hotfix*, see [Microsoft Knowledge Base Article 824684](http://support.microsoft.com/kb/824684).
This security update supports the following setup switches.
| Switch | Description |
|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------|
| **/?, /h, /help** | Displays help on supported switches. |
| **/quiet** | Suppresses the display of status or error messages. |
| **/norestart** | When combined with **/quiet**, the system will not be restarted after installation even if a restart is required to complete installation. |
**Note** For more information about the wusa.exe installer, see [Microsoft Knowledge Base Article 934307](http://support.microsoft.com/kb/934307).
**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.
1. Click **Start** and then enter an update file name in the **Start Search** box.
2. When the file appears under **Programs**, right-click the file name and click **Properties**.
3. On the **General** tab, compare the file size with the file information tables provided in the bulletin KB article.
**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.
4. You can also click the **Details** tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
**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.
5. Finally, you can also click the **Previous Versions** tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
#### Windows Server 2008 (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

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.

HotPatching

Not applicable.

Removal Information

WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.

Note A registry key does not exist to validate the presence of this update.

#### 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 terminology that appears in this bulletin, such as *hotfix*, see [Microsoft Knowledge Base Article 824684](http://support.microsoft.com/kb/824684).
This security update supports the following setup switches.
| Switch | Description |
|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------|
| **/?, /h, /help** | Displays help on supported switches. |
| **/quiet** | Suppresses the display of status or error messages. |
| **/norestart** | When combined with **/quiet**, the system will not be restarted after installation even if a restart is required to complete installation. |
**Note** For more information about the wusa.exe installer, see [Microsoft Knowledge Base Article 934307](http://support.microsoft.com/kb/934307).
**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.
1. Click **Start** and then enter an update file name in the **Start Search** box.
2. When the file appears under **Programs**, right-click the file name and click **Properties**.
3. On the **General** tab, compare the file size with the file information tables provided in the bulletin KB article.
**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.
4. You can also click the **Details** tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
**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.
5. Finally, you can also click the **Previous Versions** tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
#### Windows 7 (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

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.

HotPatching

Not applicable.

Removal Information

To uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, and then under Windows Update, click View installed updates and select from the list of updates.

Note A registry key does not exist to validate the presence of this update.

#### 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 terminology that appears in this bulletin, such as *hotfix*, see [Microsoft Knowledge Base Article 824684](http://support.microsoft.com/kb/824684).
This security update supports the following setup switches.
| Switch | Description |
|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|
| **/?, /h, /help** | Displays help on supported switches. |
| **/quiet** | Suppresses the display of status or error messages. |
| **/norestart** | When combined with **/quiet**, the system will not be restarted after installation even if a restart is required to complete installation. |
| **/warnrestart:<seconds>** | When combined with **/quiet**, the installer will warn the user before initiating restart. |
| **/promptrestart** | When combined with **/quiet**, the installer will prompt before initiating restart. |
| **/forcerestart** | When combined with **/quiet**, the installer will forcefully close applications and initiate restart. |
| **/log:<file name>** | Enables logging to specified file. |
| **/extract:<destination>** | Extracts the package contents to the destination folder. |
| **/uninstall /kb:<KB Number>** | Uninstalls the security update. |
**Note** For more information about the wusa.exe installer, see "Windows Update Stand-alone Installer" in the TechNet article, [Miscellaneous Changes in Windows 7](http://technet.microsoft.com/en-us/library/dd871148(ws.10).aspx).
**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.
1. Click **Start** and then enter an update file name in the **Search** box.
2. When the file appears under **Programs**, right-click the file name and click **Properties**.
3. On the **General** tab, compare the file size with the file information tables provided in the bulletin KB article.
**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.
4. You can also click the **Details** tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
**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.
5. Finally, you can also click the **Previous Versions** tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
#### Windows Server 2008 R2 (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

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.

HotPatching

Not applicable.

Removal Information

To uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, and then under Windows Update, click View installed updates and select from the list of updates.

Note A registry key does not exist to validate the presence of this update.

#### 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 terminology that appears in this bulletin, such as *hotfix*, see [Microsoft Knowledge Base Article 824684](http://support.microsoft.com/kb/824684).
This security update supports the following setup switches.
| Switch | Description |
|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|
| **/?, /h, /help** | Displays help on supported switches. |
| **/quiet** | Suppresses the display of status or error messages. |
| **/norestart** | When combined with **/quiet**, the system will not be restarted after installation even if a restart is required to complete installation. |
| **/warnrestart:<seconds>** | When combined with **/quiet**, the installer will warn the user before initiating restart. |
| **/promptrestart** | When combined with **/quiet**, the installer will prompt before initiating restart. |
| **/forcerestart** | When combined with **/quiet**, the installer will forcefully close applications and initiate restart. |
| **/log:<file name>** | Enables logging to specified file. |
| **/extract:<destination>** | Extracts the package contents to the destination folder. |
| **/uninstall /kb:<KB Number>** | Uninstalls the security update. |
**Note** For more information about the wusa.exe installer, see "Windows Update Stand-alone Installer" in the TechNet article, [Miscellaneous Changes in Windows 7](http://technet.microsoft.com/en-us/library/dd871148(ws.10).aspx).
**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.
1. Click **Start** and then enter an update file name in the **Start Search** box.
2. When the file appears under **Programs**, right-click the file name and click **Properties**.
3. On the **General** tab, compare the file size with the file information tables provided in the bulletin KB article.
**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.
4. You can also click the **Details** tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
**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.
5. Finally, you can also click the **Previous Versions** tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
### Other Information
#### Acknowledgments
Microsoft [thanks](http://go.microsoft.com/fwlink/?linkid=21127) the following for working with us to help protect customers:
- Abdul Aziz Hariri, working with [TippingPoint's Zero Day Initiative](http://www.zerodayinitiative.com/), for reporting the DSN Overflow Vulnerability (CVE-2011-0026)
- Peter Vreugdenhil, working with [TippingPoint's Zero Day Initiative](http://www.zerodayinitiative.com/), for reporting the ADO Record Memory Vulnerability (CVE-2011-0027)
#### Microsoft Active Protections Program (MAPP)
To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please visit the active protections Web sites provided by program partners, listed in [Microsoft Active Protections Program (MAPP) Partners](http://www.microsoft.com/security/msrc/mapp/partners.mspx).
#### Support
- Customers in the U.S. and Canada can receive technical support from [Security Support](http://go.microsoft.com/fwlink/?linkid=21131) or 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates. For more information about available support options, see [Microsoft Help and Support](http://support.microsoft.com/).
- 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](http://go.microsoft.com/fwlink/?linkid=21155).
#### 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 (January 11, 2011): Bulletin published.
*Built at 2014-04-18T13:49:36Z-07:00*