Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Microsoft Security Bulletin MS11-049 - Important

Vulnerability in the Microsoft XML Editor Could Allow Information Disclosure

Published: June 14, 2011 | Updated: February 15, 2012

Version: 2.4

General Information

Executive Summary

This security update resolves a privately reported vulnerability in Microsoft XML Editor. The vulnerability could allow information disclosure if a user opened a specially crafted Web Service Discovery (.disco) file with one of the affected software listed in this bulletin. Note that this vulnerability would not allow an attacker to execute code or to elevate their user rights directly, but it could be used to produce information that could be used to try to further compromise the affected system.

This security update is rated Important for all supported editions of Microsoft InfoPath 2007 and Microsoft InfoPath 2010; all supported editions of SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2; and all supported editions of Microsoft Visual Studio 2005, Microsoft Visual Studio 2008, and Microsoft Visual Studio 2010. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerability by correcting the manner in which the XML Editor resolves external entities within a Web Service Discovery (.disco) file. For more information about the vulnerability, 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 2543893 documents the currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues.

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.

Microsoft Office Software

SoftwareMaximum Security ImpactAggregate Severity RatingBulletins Replaced by this Update
Microsoft InfoPath 2007 Service Pack 2
(KB2510061)
Information DisclosureImportantNone
Microsoft InfoPath 2010 (32-bit editions)
(KB2510065)
Information DisclosureImportantNone
Microsoft InfoPath 2010 (64-bit editions)
(KB2510065)
Information DisclosureImportantNone

Microsoft SQL Server

GDR Software UpdatesQFE Software UpdatesMaximum Security ImpactAggregate Severity RatingBulletins Replaced by this Update
SQL Server 2005 Service Pack 3
(KB2494113)
SQL Server 2005 Service Pack 3
(KB2494112)
Information DisclosureImportantMS09-062
SQL Server 2005 x64 Edition Service Pack 3
(KB2494113)
SQL Server 2005 x64 Edition Service Pack 3
(KB2494112)
Information DisclosureImportantMS09-062
SQL Server 2005 for Itanium-based Systems Service Pack 3
(KB2494113)
SQL Server 2005 for Itanium-based Systems Service Pack 3
(KB2494112)
Information DisclosureImportantMS09-062
SQL Server 2005 Service Pack 4
(KB2494120)
SQL Server 2005 Service Pack 4
(KB2494123)
Information DisclosureImportantNone
SQL Server 2005 x64 Edition Service Pack 4
(KB2494120)
SQL Server 2005 x64 Edition Service Pack 4
(KB2494123)
Information DisclosureImportantNone
SQL Server 2005 for Itanium-based Systems Service Pack 4
(KB2494120)
SQL Server 2005 for Itanium-based Systems Service Pack 4
(KB2494123)
Information DisclosureImportantNone
SQL Server 2005 Express Edition Service Pack 3
(KB2494113)
SQL Server 2005 Express Edition Service Pack 3
(KB2494112)
Information DisclosureImportantNone
SQL Server 2005 Express Edition Service Pack 4
(KB2494120)
SQL Server 2005 Express Edition Service Pack 4
(KB2494123)
Information DisclosureImportantNone
SQL Server 2005 Express Edition with Advanced Services Service Pack 3
(KB2494113)
SQL Server 2005 Express Edition with Advanced Services Service Pack 3
(KB2494112)
Information DisclosureImportantNone
SQL Server 2005 Express Edition with Advanced Services Service Pack 4
(KB2494120)
SQL Server 2005 Express Edition with Advanced Services Service Pack 4
(KB2494123)
Information DisclosureImportantNone
SQL Server Management Studio Express (SSMSE) 2005
(KB2546869)
Not applicableInformation DisclosureImportantNone
SQL Server Management Studio Express (SSMSE) 2005 x64 Edition
(KB2546869)
Not applicableInformation DisclosureImportantNone
SQL Server 2008 for 32-bit Systems Service Pack 1[1]
(KB2494096)
SQL Server 2008 for 32-bit Systems Service Pack 1[1]
(KB2494100)
Information DisclosureImportantNone
SQL Server 2008 for x64-based Systems Service Pack 1[1]
(KB2494096)
SQL Server 2008 for x64-based Systems Service Pack 1[1]
(KB2494100)
Information DisclosureImportantNone
SQL Server 2008 for Itanium-based Systems Service Pack 1
(KB2494096)
SQL Server 2008 for Itanium-based Systems Service Pack 1
(KB2494100)
Information DisclosureImportantNone
SQL Server 2008 for 32-bit Systems Service Pack 2[1]
(KB2494089)
SQL Server 2008 for 32-bit Systems Service Pack 2[1]
(KB2494094)
Information DisclosureImportantNone
SQL Server 2008 for x64-based Systems Service Pack 2[1]
(KB2494089)
SQL Server 2008 for x64-based Systems Service Pack 2[1]
(KB2494094)
Information DisclosureImportantNone
SQL Server 2008 for Itanium-based Systems Service Pack 2
(KB2494089)
SQL Server 2008 for Itanium-based Systems Service Pack 2
(KB2494094)
Information DisclosureImportantNone
SQL Server 2008 R2 for 32-bit Systems[1]
(KB2494088)
SQL Server 2008 R2 for 32-bit Systems[1]
(KB2494086)
Information DisclosureImportantNone
SQL Server 2008 R2 for x64-based Systems[1]
(KB2494088)
SQL Server 2008 R2 for x64-based Systems[1]
(KB2494086)
Information DisclosureImportantNone
SQL Server 2008 R2 for Itanium-based Systems
(KB2494088)
SQL Server 2008 R2 for Itanium-based Systems
(KB2494086)
Information DisclosureImportantNone

[1]This update also applies to the corresponding Express and Express with Advanced Services Editions.

Developer Tools

SoftwareMaximum Security ImpactAggregate Severity RatingBulletins Replaced by this Update
Microsoft Visual Studio 2005 Service Pack 1
(KB2251481)
Information DisclosureImportantNone
Microsoft Visual Studio 2008 Service Pack 1
(KB2251487)
Information DisclosureImportantNone
Microsoft Visual Studio 2010
(KB2251489)
Information DisclosureImportantNone

Non-Affected Software

Operating System
Microsoft InfoPath 2003 Service Pack 3
Microsoft SQL Server 2000 Desktop Engine Service Pack 4
Microsoft SQL Server 2000 Itanium Edition Service Pack 4
Microsoft SQL Server 2000 Reporting Services Service Pack 2
Microsoft SQL Server 2000 Service Pack 4
Microsoft Visual Studio .NET 2003 Service Pack 1

Why was this bulletin revised on January 24, 2012? 
Microsoft revised this bulletin to announce a detection change for KB2251481, KB2251487, and KB2251489 to correct an installation issue. This is a detection change only. There were no changes to the security update files. Customers who have already successfully updated their systems do not need to take any action.

Why was this bulletin revised on September 13, 2011? 
Microsoft revised this security bulletin to announce a detection change in the package for KB2494089 to correct an installation issue. This is a detection change only. Customers who have already successfully updated their systems do not need to take any action.

Why was this bulletin rereleased on August 9, 2011? 
Microsoft rereleased this bulletin to announce a detection change to the update for Microsoft Visual Studio 2005 Service Pack 1 (KB2251481) to add detection for the following related software:

  • Microsoft Visual Studio 2005 Tools for Office (all languages)
  • Microsoft Visual Basic 2005 Express Edition (all languages)
  • Microsoft Visual C++ 2005 Express Edition (all languages)
  • Microsoft Visual C# 2005 Express Edition (all languages)
  • Microsoft Visual J# 2005 Express Edition (all languages)
  • Microsoft Visual Web Developer 2005 Express Edition (all languages)
  • Microsoft Visual Studio 2005 Premier Partner Edition (all languages)

This is a detection change only. There were no changes to the security update files in this bulletin. Customers who have already successfully updated their systems do not need to reinstall this update.

There are both GDR and QFE updates offered for my version of SQL. How do I know which update to use? 
First, determine your SQL Server version number. For more information on determining your SQL Server version number, see Microsoft Knowledge Base Article 321185.

Second, in the table below, locate the version range that your SQL Server version number falls within. The corresponding update is the update you need to install.

Note If your SQL Server version number does not fall within any of the ranges in the table below, your SQL Server version is no longer supported. Please upgrade to the latest Service Pack or SQL Server product in order to apply this and future security updates.

For SQL Server 2005:

SQL Server Version Range
9.00.4035-9.00.40599.00.4205-9.00.43399.00.5000-9.00.50569.00.5254-9.00.5291
SQL Server Update
SQL Server 2005 Service Pack 3 GDR
(KB2494113)
SQL Server 2005 Service Pack 3 QFE
(KB2494112)
SQL Server 2005 Service Pack 4 GDR
(KB2494120)
SQL Server 2005 Service Pack 4 QFE
(KB2494123)

For SQL Server 2008:

SQL Server Version Range
10.00.2531-10.00.257210.00.2710-10.00.284010.00.4000-10.00.406310.00.4260-10.00.4310
SQL Server Update
SQL Server 2008 Service Pack 1 GDR
(KB2494096)
SQL Server 2008 Service Pack 1 QFE
(KB2494100)
SQL Server 2008 Service Pack 2 GDR
(KB2494089)
SQL Server 2008 Service Pack 2 QFE
(KB2494094)

For SQL Server 2008 R2:

SQL Server Version Range
10.50.1600.1-10.50.161610.50.1701-10.50.1789
SQL Server Update
SQL Server 2008 R2 GDR
(KB2494088)
SQL Server 2008 R2 QFE
(KB2494086)

For additional installation instructions, see the Security Update Information subsection for your SQL Server edition in the Update Information section.

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.

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 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. For more information about service packs for these software releases, see Lifecycle Supported Service Packs.

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 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.

Vulnerability Information

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 June bulletin summary. For more information, see Microsoft Exploitability Index.

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected SoftwareXML External Entities Resolution Vulnerability - CVE-2011-1280Aggregate Severity Rating
Microsoft InfoPath
Microsoft InfoPath 2007 Service Pack 2Important 
Information Disclosure
Important
Microsoft InfoPath 2010 (32-bit editions)Important 
Information Disclosure
Important
Microsoft InfoPath 2010 (64-bit editions)Important 
Information Disclosure
Important
Microsoft SQL Server
SQL Server 2005 Service Pack 3Important 
Information Disclosure
Important
SQL Server 2005 x64 Edition Service Pack 3Important 
Information Disclosure
Important
SQL Server 2005 for Itanium-based Systems Service Pack 3Important 
Information Disclosure
Important
SQL Server 2005 Service Pack 4Important 
Information Disclosure
Important
SQL Server 2005 x64 Edition Service Pack 4Important 
Information Disclosure
Important
SQL Server 2005 for Itanium-based Systems Service Pack 4Important 
Information Disclosure
Important
SQL Server 2008 for 32-bit Systems Service Pack 1Important 
Information Disclosure
Important
SQL Server 2008 for x64-based Systems Service Pack 1Important 
Information Disclosure
Important
SQL Server 2008 for Itanium-based Systems Service Pack 1Important 
Information Disclosure
Important
SQL Server 2008 for 32-bit Systems Service Pack 2Important 
Information Disclosure
Important
SQL Server 2008 for x64-based Systems Service Pack 2Important 
Information Disclosure
Important
SQL Server 2008 for Itanium-based Systems Service Pack 2Important 
Information Disclosure
Important
SQL Server 2008 R2 for 32-bit Systems Important 
Information Disclosure
Important
SQL Server 2008 R2 for x64-based Systems Important 
Information Disclosure
Important
SQL Server 2008 R2 for Itanium-based Systems Important 
Information Disclosure
Important
SQL Server 2005 Express Edition Service Pack 3Important 
Information Disclosure
Important
SQL Server 2005 Express Edition Service Pack 4Important 
Information Disclosure
Important
SQL Server 2005 Express Edition with Advanced Services Service Pack 3Important 
Information Disclosure
Important
SQL Server 2005 Express Edition with Advanced Services Service Pack 4Important 
Information Disclosure
Important
SQL Server Management Studio Express (SSMSE) 2005Important 
Information Disclosure
Important
SQL Server Management Studio Express (SSMSE) 2005 x64 EditionImportant 
Information Disclosure
Important
Microsoft Visual Studio
Microsoft Visual Studio 2005 Service Pack 1Important 
Information Disclosure
Important
Microsoft Visual Studio 2008 Service Pack 1Important 
Information Disclosure
Important
Microsoft Visual Studio 2010Important 
Information Disclosure
Important

An information disclosure vulnerability exists in the way that Microsoft XML Editor handles specially crafted XML files.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2011-1280.

Mitigating Factors for XML External Entities Resolution Vulnerability - CVE-2011-1280

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:

  • The vulnerability cannot be exploited automatically through e-mail. For an attack to be successful a user must open an attachment that is sent in an e-mail message.
  • 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 convince 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.

Workarounds for XML External Entities Resolution Vulnerability - CVE-2011-1280

Microsoft has not identified any workarounds for this vulnerability.

FAQ for XML External Entities Resolution Vulnerability - CVE-2011-1280

What is the scope of the vulnerability? 
This is an information disclosure vulnerability. An attacker who successfully exploited this vulnerability could read data from a file located on the target system. Note that this vulnerability would not allow an attacker to execute code or to elevate their user rights directly, but it could be used to produce information that could be used to try to further compromise the affected system.

What causes the vulnerability? 
The vulnerability is due to the fact that XML external entities are resolved within other XML external entity declarations.

What is the XML Editor? 
The XML Editor is the editor for XML files. It can be used on a stand-alone XML file, or on a file associated with a Visual Studio project. If a schema or document type definition is provided, it is used by IntelliSense to list allowable elements and attributes. The XML Editor is associated with the following file extensions: .config, .dtd, .xml, .xsd, .xdr, .xsl, .xslt, and .vssettings. The XML Editor is also associated with any other file type that has no specific editor registered, and that contains XML or DTD content. For more information on the XML Editor, see the MSDN article, XML Editor.

What is a Web Service Discovery (.disco) File? 
The .disco document is an XML document that simply contains links to other resources that describe the Web Service, much like an HTML file that contains human-readable documentation or a WSDL file containing the interface contract.

What is an XML External Entity? 
An XML document may consist of one or many storage units. These are called entities. They all have content and are all identified by entity name. External entities allow an XML document to refer to an external file. External entities contain either text or binary data. If they contain text, the content of the external file is inserted at the point of reference and parsed as part of the referring document. For more information, see the specification.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability would be able to read data from files on the target system. Note that this vulnerability would not allow an attacker to execute code or to elevate their user rights directly, but it could be used to produce information that could be used to try to further compromise the affected system.

How could an attacker exploit the vulnerability? 
For an attacker to exploit this vulnerability, a user would need to open a specially crafted Web Service Discovery (.disco) file with one of the applications listed in the Affected Software table.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted Web Service Discovery (.disco) file to the user and by convincing the user to open the file within one of the applications listed in the Affected Software table.

In a Web-based attack scenario, an attacker would have to host a Web site that contains a specially crafted Web Service Discovery (.disco) file that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site, and then convince them to open the specially crafted Web Service Discovery (.disco) file.

What systems are primarily at risk from the vulnerability? 
This vulnerability requires that a user open a malicious XML file with an affected application for any malicious action to occur. Therefore, any systems where XML files frequently viewed, such as workstations or terminal servers, are at the most risk from this vulnerability.

What does the update do? 
The update addresses the vulnerability by correcting the manner in which the XML Editor resolves external entities within a Web Service Discovery (.disco) file.

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.

Update Information

Security Central

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 and Windows 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 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.

Software MBSA
Microsoft InfoPath 2007 Service Pack 2Yes
Microsoft InfoPath 2010 (32-bit editions)Yes
Microsoft InfoPath 2010 (64-bit editions)Yes
SQL Server 2005 Service Pack 3Yes
SQL Server 2005 x64 Edition Service Pack 3Yes
SQL Server 2005 for Itanium-based Systems Service Pack 3Yes
SQL Server 2005 Service Pack 4Yes
SQL Server 2005 x64 Edition Service Pack 4Yes
SQL Server 2005 for Itanium-based Systems Service Pack 4Yes
SQL Server 2008 for 32-bit Systems Service Pack 1Yes
SQL Server 2008 for x64-based Systems Service Pack 1Yes
SQL Server 2008 for Itanium-based Systems Service Pack 1Yes
SQL Server 2008 for 32-bit Systems Service Pack 2Yes
SQL Server 2008 for x64-based Systems Service Pack 2Yes
SQL Server 2008 for Itanium-based Systems Service Pack 2Yes
SQL Server 2008 R2 for 32-bit Systems Yes
SQL Server 2008 R2 for x64-based Systems Yes
SQL Server 2008 R2 for Itanium-based Systems Yes
SQL Server 2005 Express Edition Service Pack 3Yes
SQL Server 2005 Express Edition Service Pack 4Yes
SQL Server 2005 Express Edition with Advanced Services Service Pack 3Yes
SQL Server 2005 Express Edition with Advanced Services Service Pack 4Yes
SQL Server Management Studio Express (SSMSE) 2005Yes
SQL Server Management Studio Express (SSMSE) 2005 x64 EditionYes
Microsoft Visual Studio 2005 Service Pack 1Yes
Microsoft Visual Studio 2008 Service Pack 1Yes
Microsoft Visual Studio 2010Yes

Note For customers using legacy software not supported by the latest release of MBSA, Microsoft Update, and Windows Server Update Services, please visit Microsoft Baseline Security Analyzer and reference the Legacy Product Support section on how to create comprehensive security update detection with legacy tools.

Windows Server Update Services

Windows Server Update Services (WSUS) enables information technology administrators to deploy the latest Microsoft product updates to computers that are running the Windows operating system. For more information about how to deploy security updates using Windows Server Update Services, see the TechNet article, Windows Server Update Services.

Systems Management Server

The following table provides the SMS detection and deployment summary for this security update.

SoftwareSMS 2003 with ITMUConfiguration Manager 2007
Microsoft InfoPath 2007 Service Pack 2YesYes
Microsoft InfoPath 2010 (32-bit editions)YesYes
Microsoft InfoPath 2010 (64-bit editions)YesYes
SQL Server 2005 Service Pack 3YesYes
SQL Server 2005 x64 Edition Service Pack 3YesYes
SQL Server 2005 for Itanium-based Systems Service Pack 3YesYes
SQL Server 2005 Service Pack 4YesYes
SQL Server 2005 x64 Edition Service Pack 4YesYes
SQL Server 2005 for Itanium-based Systems Service Pack 4YesYes
SQL Server 2008 for 32-bit Systems Service Pack 1YesYes
SQL Server 2008 for x64-based Systems Service Pack 1YesYes
SQL Server 2008 for Itanium-based Systems Service Pack 1YesYes
SQL Server 2008 for 32-bit Systems Service Pack 2YesYes
SQL Server 2008 for x64-based Systems Service Pack 2YesYes
SQL Server 2008 for Itanium-based Systems Service Pack 2YesYes
SQL Server 2008 R2 for 32-bit Systems YesYes
SQL Server 2008 R2 for x64-based Systems YesYes
SQL Server 2008 R2 for Itanium-based Systems YesYes
SQL Server 2005 Express Edition Service Pack 3YesYes
SQL Server 2005 Express Edition Service Pack 4YesYes
SQL Server 2005 Express Edition with Advanced Services Service Pack 3YesYes
SQL Server 2005 Express Edition with Advanced Services Service Pack 4YesYes
SQL Server Management Studio Express (SSMSE) 2005YesYes
SQL Server Management Studio Express (SSMSE) 2005 x64 EditionYesYes
Microsoft Visual Studio 2005 Service Pack 1YesYes
Microsoft Visual Studio 2008 Service Pack 1YesYes
Microsoft Visual Studio 2010YesYes

Note Microsoft discontinued support for SMS 2.0 on April 12, 2011. For SMS 2003, Microsoft also discontinued support for the Security Update Inventory Tool (SUIT) on April 12, 2011. Customers are encouraged to upgrade to System Center Configuration Manager 2007. For customers remaining on SMS 2003 Service Pack 3, the Inventory Tool for Microsoft Updates (ITMU) is also an option.

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. For more information about SMS scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.

System Center Configuration Manager 2007 uses WSUS 3.0 for detection of updates. For more information about Configuration Manager 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.

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.

Affected Software

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

InfoPath 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 PacksThe update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventioninfopath2007-kb2510061-fullfile-x86-glb.exe /passive
Installing without restartinginfopath2007-kb2510061-fullfile-x86-glb.exe /norestart
Update log fileNot applicable
Further informationFor detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance.
Restart Requirement
Restart required?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.
HotpatchingNot applicable
Removal InformationUse Add or Remove Programs tool in Control Panel.
File InformationSee Microsoft Knowledge Base Article 2510061
Registry Key VerificationNot applicable

Deployment Information

Installing the Update

You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.

This security update requires that Windows Installer 3.1 or later be installed on the system.

To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft Web sites:

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.

Supported Security Update Installation Switches
SwitchDescription
/? or /helpDisplays usage dialog.
/passiveSpecifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel.
/quietSpecifies quiet mode, or suppresses prompts, when files are being extracted.
/norestartSuppresses restarting the system if the update requires a restart.
/forcerestartAutomatically restarts the system after applying the update, regardless of whether the update requires the restart.
/extractExtracts the files without installing them. You are prompted for a target folder.
/extract:<path>Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file.
/lang:<LCID>Forces the use of a specific language, when the update package supports that language.
/log:<log file>Enables logging, by both Vnox and Installer, during the update installation.

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.

Removing the Update

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

Note When you remove this update, you may be prompted to insert the 2007 Microsoft Office CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.

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 Start Search.
    2. When the file appears under Programs, right-click on the file name and click Properties.
    3. Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
    4. You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
    5. Finally, you may also click on 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.

InfoPath 2010 (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 PacksThe update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventionFor all supported 32-bit editions of InfoPath 2010:
infopath2010-kb2510065-fullfile-x86-glb.exe /passive
For all supported x64-based editions of InfoPath 2010:
InfoPath2010-kb2510065-fullfile-x64-glb.exe /passive
Installing without restartingFor all supported 32-bit editions of InfoPath 2010:
infopath2010-kb2510065-fullfile-x86-glb.exe /norestart
For all supported x64-based editions of InfoPath 2010:
InfoPath2010-kb2510065-fullfile-x64-glb.exe /norestart
Update log fileNot applicable
Further informationFor detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance.
Restart Requirement
Restart required?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.
HotpatchingNot applicable
Removal InformationUse Add or Remove Programs tool in Control Panel.
File InformationSee Microsoft Knowledge Base Article 2510065
Registry Key VerificationNot applicable

Deployment Information

Installing the Update

You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.

This security update requires that Windows Installer 3.1 or later be installed on the system.

To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft Web sites:

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.

Supported Security Update Installation Switches
SwitchDescription
/? or /helpDisplays usage dialog.
/passiveSpecifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel.
/quietSpecifies quiet mode, or suppresses prompts, when files are being extracted.
/norestartSuppresses restarting the system if the update requires a restart.
/forcerestartAutomatically restarts the system after applying the update, regardless of whether the update requires the restart.
/extractExtracts the files without installing them. You are prompted for a target folder.
/extract:<path>Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file.
/lang:<LCID>Forces the use of a specific language, when the update package supports that language.
/log:<log file>Enables logging, by both Vnox and Installer, during the update installation.

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.

Removing the Update

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

Note When you remove this update, you may be prompted to insert the 2007 Microsoft Office CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.

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 Start Search.
    2. When the file appears under Programs, right-click on the file name and click Properties.
    3. Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
    4. You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
    5. Finally, you may also click on 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.

SQL Server 2005 (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 PacksSQL Server 2005 Service Pack 5
Deployment
Installing without user interventionFor GDR update of all supported 32-bit editions of SQL Server 2005 Service Pack 3:
SQLServer2005-KB2494113-x86-enu.exe /quiet /allinstances
For GDR update of all supported x64-based editions of SQL Server 2005 Service Pack 3:
SQLServer2005-KB2494113-x64-enu.exe /quiet /allinstances
For GDR update of all supported Itanium-based editions of SQL Server 2005 Service Pack 3:
SQLServer2005-KB2494113-ia64-enu.exe /quiet /allinstances
For QFE update of all supported 32-bit editions of SQL Server 2005 Service Pack 3:
SQLServer2005-KB2494112-x86-enu.exe /quiet /allinstances
For QFE update of all supported x64-based editions of SQL Server 2005 Service Pack 3:
SQLServer2005-KB2494112-x64-enu.exe /quiet /allinstances
For QFE update of all supported Itanium-based editions of SQL Server 2005 Service Pack 3:
SQLServer2005-KB2494112-ia64-enu.exe /quiet /allinstances
For GDR update of all supported 32-bit editions of SQL Server 2005 Service Pack 4:
SQLServer2005-KB2494120-x86-enu.exe /quiet /allinstances
For GDR update of all supported x64-based editions of SQL Server 2005 Service Pack 4:
SQLServer2005-KB2494120-x64-enu.exe /quiet /allinstances
For GDR update of all supported Itanium-based editions of SQL Server 2005 Service Pack 4:
SQLServer2005-KB2494120-ia64-enu.exe /quiet /allinstances
For QFE update of all supported 32-bit editions of SQL Server 2005 Service Pack 4:
SQLServer2005-KB2494123-x86-enu.exe /quiet /allinstances
For QFE update of all supported x64-based editions of SQL Server 2005 Service Pack 4:
SQLServer2005-KB2494123-x64-enu.exe /quiet /allinstances
For QFE update of all supported Itanium-based editions of SQL Server 2005 Service Pack 4:
SQLServer2005-KB2494123-ia64-enu.exe /quiet /allinstances
For SQL Server Management Studio Express (SSMSE) 2005:
SSMSEE-KB2546869-x86.exe /quiet /allinstances
For SQL Server Management Studio Express (SSMSE) 2005 x64 Edition:
SSMSEE-KB2546869-x64.exe /quiet /allinstances
Installing a single instanceFor GDR update of all supported 32-bit editions of SQL Server 2005 Service Pack 3:
SQLServer2005-KB2494113-x86-enu.exe /quiet /InstanceName={instance}
For GDR update of all supported x64-based editions of SQL Server 2005 Service Pack 3:
SQLServer2005-KB2494113-x64-enu.exe /quiet /InstanceName={instance}
For GDR update of all supported Itanium-based editions of SQL Server 2005 Service Pack 3:
SQLServer2005-KB2494113-ia64-enu.exe /quiet /InstanceName={instance}
For QFE update of all supported 32-bit editions of SQL Server 2005 Service Pack 3:
SQLServer2005-KB2494112-x86-enu.exe /quiet /InstanceName={instance}
For QFE update of all supported x64-based editions of SQL Server 2005 Service Pack 3:
SQLServer2005-KB2494112-x64-enu.exe /quiet /InstanceName={instance}
For QFE update of all supported Itanium-based editions of SQL Server 2005 Service Pack 3:
SQLServer2005-KB2494112-ia64-enu.exe /quiet /InstanceName={instance}
For GDR update of all supported 32-bit editions of SQL Server 2005 Service Pack 4:
SQLServer2005-KB2494120-x86-enu.exe /quiet /InstanceName={instance}
For GDR update of all supported x64-based editions of SQL Server 2005 Service Pack 4:
SQLServer2005-KB2494120-x64-enu.exe /quiet /InstanceName={instance}
For GDR update of all supported Itanium-based editions of SQL Server 2005 Service Pack 4:
SQLServer2005-KB2494120-ia64-enu.exe /quiet /InstanceName={instance}
For QFE update of all supported 32-bit editions of SQL Server 2005 Service Pack 4:
SQLServer2005-KB2494123-x86-enu.exe /quiet /InstanceName={instance}
For QFE update of all supported x64-based editions of SQL Server 2005 Service Pack 4:
SQLServer2005-KB2494123-x64-enu.exe /quiet /InstanceName={instance}
For QFE update of all supported Itanium-based editions of SQL Server 2005 Service Pack 4:
SQLServer2005-KB2494123-ia64-enu.exe /quiet /InstanceName={instance}
For SQL Server Management Studio Express (SSMSE) 2005:
SSMSEE-KB2546869-x86.exe /quiet /InstanceName={instance}
For SQL Server Management Studio Express (SSMSE) 2005 x64 Edition:
SSMSEE-KB2546869-x64.exe /quiet /InstanceName={instance}
Update log file%programfiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Summary.log
Special instructionsThe update will also be offered to SQL Server 2005 instances that are clustered. Updates for SQL Server 2005 clusters will require user interaction.

If your SQL Server 2005 cluster has a passive node, Microsoft recommends that you scan and apply the update to the active node first, and then scan and apply to the passive node. When all components have been updated on the passive node, the update will no longer be offered.
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?If a restart is required, the installer will prompt or return exit code 3010.
HotpatchingThis security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341.
Removal InformationFor all supported editions of SQL Server 2005:
Use Add or Remove Programs tool in Control Panel
File InformationFor GDR update of SQL Server 2005 Service Pack 3:
see Microsoft Knowledge Base Article 2494113
For QFE update of SQL Server 2005 Service Pack 3:
see Microsoft Knowledge Base Article 2494112
For GDR update of SQL Server 2005 Service Pack 4:
see Microsoft Knowledge Base Article 2494120
For QFE update of SQL Server 2005 Service Pack 4:
see Microsoft Knowledge Base Article 2494123
For SQL Server Management Studio Express (SSMSE) 2005:
see Microsoft Knowledge Base Article 2546869

Deployment Information

Installing the Update

When you install this security update, the installer checks to see if 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.

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/?Displays the Help dialog
/quietRuns Setup in quiet mode
/reportonlyDisplays the features that this package can update
/allinstancesUpgrades all SQL Server instances and all shared components
/instancenameUpgrades a specific SQL Server instance and all shared components
/sapwdPassword for the SQL Server sa account to run scripts
/userUser account for connecting to a remote cluster node
/passwordPassword for user account for connecting to a remote cluster node
/rsupgradedatabaseaccountUser account for upgrading Reporting Services
/rsupgradepasswordPassword for user account for upgrading Reporting Services
/rsupgradedatabasePrevents the Reporting Services database from being upgraded when the parameter equals 0
/allinstancesApplies update to all instances
/InstanceName={instance}Applies update to specified instance

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. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.

Removing the Update

Example of how to remove QFE from single instance:

%windir%\SQL9_KB960090_ENU\hotfix.exe /quiet /uninstall /instancename=foo

Example of how to remove QFE from all instances:

%windir%\SQL9_KB960090_ENU\hotfix.exe /quiet /uninstall /allinstances

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 versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
    5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate 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.

SQL 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 PacksSQL Server 2008 Service Pack 3
Deployment
Installing without user interventionFor GDR update of SQL Server 2008 Service Pack 1:
SQLServer2008-KB2494096-x86-enu.exe /quiet /allinstances
For GDR update of SQL Server 2008 x64 Edition Service Pack 1:
SQLServer2008-KB2494096-x64-enu.exe /quiet /allinstances
For GDR update of SQL Server 2008 for Itanium-based Systems Service Pack 1:
SQLServer2008-KB2494096-ia64-enu.exe /quiet /allinstances
For QFE update of SQL Server 2008 Service Pack 1:
SQLServer2008-KB2494100-x86-enu.exe /quiet /allinstances
For QFE update of SQL Server 2008 x64 Edition Service Pack 1:
SQLServer2008-KB2494100-x64-enu.exe /quiet /allinstances
For QFE update of SQL Server 2008 for Itanium-based Systems Service Pack 1:
SQLServer2008-KB2494100-ia64-enu.exe /quiet /allinstances
For GDR update of SQL Server 2008 Service Pack 2:
SQLServer2008-KB2494089-x86-enu.exe /quiet /allinstances
For GDR update of SQL Server 2008 x64 Edition Service Pack 2:
SQLServer2008-KB2494089-x64-enu.exe /quiet /allinstances
For GDR update of SQL Server 2008 for Itanium-based Systems Service Pack 2:
SQLServer2008-KB2494089-ia64-enu.exe /quiet /allinstances
For QFE update of SQL Server 2008 Service Pack 2:
SQLServer2008-KB2494094-x86-enu.exe /quiet /allinstances
For QFE update of SQL Server 2008 x64 Edition Service Pack 2:
SQLServer2008-KB2494094-x64-enu.exe /quiet /allinstances
For QFE update of SQL Server 2008 for Itanium-based Systems Service Pack 2:
SQLServer2008-KB2494094-ia64-enu.exe /quiet /allinstances
Installing a single instanceFor GDR update of SQL Server 2008 Service Pack 1:
SQLServer2008-KB2494096-x86-enu.exe /quiet /InstanceName={instance}
For GDR update of SQL Server 2008 x64 Edition Service Pack 1:
SQLServer2008-KB2494096-x64-enu.exe /quiet /InstanceName={instance}
For GDR update of SQL Server 2008 for Itanium-based Systems Service Pack 1:
SQLServer2008-KB2494096-ia64-enu.exe /quiet /InstanceName={instance}
For QFE update of SQL Server 2008 Service Pack 1:
SQLServer2008-KB2494100-x86-enu.exe /quiet /InstanceName={instance}
For QFE update of SQL Server 2008 x64 Edition Service Pack 1:
SQLServer2008-KB2494100-x64-enu.exe /quiet /InstanceName={instance}
For QFE update of SQL Server 2008 for Itanium-based Systems Service Pack 1:
SQLServer2008-KB2494100-ia64-enu.exe /quiet /InstanceName={instance}
For GDR update of SQL Server 2008 Service Pack 2:
SQLServer2008-KB2494089-x86-enu.exe /quiet /InstanceName={instance}
For GDR update of SQL Server 2008 x64 Edition Service Pack 2:
SQLServer2008-KB2494089-x64-enu.exe /quiet /InstanceName={instance}
For GDR update of SQL Server 2008 for Itanium-based Systems Service Pack 2:
SQLServer2008-KB2494089-ia64-enu.exe /quiet /InstanceName={instance}
For QFE update of SQL Server 2008 Service Pack 2:
SQLServer2008-KB2494094-x86-enu.exe /quiet /InstanceName={instance}
For QFE update of SQL Server 2008 x64 Edition Service Pack 2:
SQLServer2008-KB2494094-x64-enu.exe /quiet /InstanceName={instance}
For QFE update of SQL Server 2008 for Itanium-based Systems Service Pack 2:
SQLServer2008-KB2494094-ia64-enu.exe /quiet /InstanceName={instance}
Update log file%programfiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Summary.log
Special instructionsThe update will also be offered to SQL Server 2008 instances that are clustered. Updates for SQL Server 2008 clusters will require user interaction.

If your SQL Server 2008 cluster has a passive node, Microsoft recommends that you scan and apply the update to the active node first, and then scan and apply to the passive node. When all components have been updated on the passive node, the update will no longer be offered.
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?If a restart is required, the installer will prompt or return exit code 3010.
HotpatchingThis security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341.
Removal InformationFor all supported editions of SQL Server 2005:
Use Add or Remove Programs tool in Control Panel
File InformationFor GDR update of SQL Server 2008 Service Pack 1:
see Microsoft Knowledge Base Article 2494096
For QFE update of SQL Server 2008 Service Pack 1:
see Microsoft Knowledge Base Article 2494100
For GDR update of SQL Server 2008 Service Pack 2:
see Microsoft Knowledge Base Article 2494089
For QFE update of SQL Server 2008 Service Pack 2:
see Microsoft Knowledge Base Article 2494094

Deployment Information

Installing the Update

When you install this security update, the installer checks to see if 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.

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/?Displays the Help dialog
/quietRuns Setup in quiet mode
/reportonlyDisplays the features that this package can update
/allinstancesUpgrades all SQL Server instances and all shared components
/instancenameUpgrades a specific SQL Server instance and all shared components
/sapwdPassword for the SQL Server sa account to run scripts
/userUser account for connecting to a remote cluster node
/passwordPassword for user account for connecting to a remote cluster node
/rsupgradedatabaseaccountUser account for upgrading Reporting Services
/rsupgradepasswordPassword for user account for upgrading Reporting Services
/rsupgradedatabasePrevents the Reporting Services database from being upgraded when the parameter equals 0
/allinstancesApplies update to all instances
/InstanceName={instance}Applies update to specified instance

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. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.

Removing the Update

Example of how to remove QFE from single instance:

%windir%\SQL9_KB960090_ENU\hotfix.exe /quiet /uninstall /instancename=foo

Example of how to remove QFE from all instances:

%windir%\SQL9_KB960090_ENU\hotfix.exe /quiet /uninstall /allinstances

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 versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
    5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate 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.

SQL Server 2008 R2

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 PacksSQL Server 2008 R2 Service Pack 1
Deployment
Installing without user interventionFor GDR update of SQL Server 2008 R2:
SQLServer2008R2-KB2494088-x86-enu.exe /quiet /allinstances
For GDR update of SQL Server 2008 R2 x64 Edition:
SQLServer2008R2-KB2494088-x64-enu.exe /quiet /allinstances
For GDR update of SQL Server 2008 R2 for Itanium-based Systems:
SQLServer2008R2-KB2494088-ia64-enu.exe /quiet /allinstances
For QFE update of SQL Server 2008 R2:
SQLServer2008R2-KB2494086-x86-enu.exe /quiet /allinstances
For QFE update of SQL Server 2008 R2 x64 Edition:
SQLServer2008R2-KB2494086-x64-enu.exe /quiet /allinstances
For QFE update of SQL Server 2008 R2 for Itanium-based Systems:
SQLServer2008R2-KB2494086-ia64-enu.exe /quiet /allinstances
Installing a single instanceFor GDR update of SQL Server 2008 R2:
SQLServer2008R2-KB2494088-x86-enu.exe /quiet /InstanceName={instance}
For GDR update of SQL Server 2008 R2 x64 Edition:
SQLServer2008R2-KB2494088-x64-enu.exe /quiet /InstanceName={instance}
For GDR update of SQL Server 2008 R2 for Itanium-based Systems:
SQLServer2008R2-KB2494088-ia64-enu.exe /quiet /InstanceName={instance}
For QFE update of SQL Server 2008 R2:
SQLServer2008R2-KB2494086-x86-enu.exe /quiet /InstanceName={instance}
For QFE update of SQL Server 2008 R2 x64 Edition:
SQLServer2008R2-KB2494086-x64-enu.exe /quiet /InstanceName={instance}
For QFE update of SQL Server 2008 R2 for Itanium-based Systems:
SQLServer2008R2-KB2494086-ia64-enu.exe /quiet /InstanceName={instance}
Update log file%programfiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Summary.log
Special instructionsThe update will also be offered to SQL Server 2008 instances that are clustered. Updates for SQL Server 2008 clusters will require user interaction.

If your SQL Server 2008 cluster has a passive node, Microsoft recommends that you scan and apply the update to the active node first, and then scan and apply to the passive node. When all components have been updated on the passive node, the update will no longer be offered.
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?If a restart is required, the installer will prompt or return exit code 3010.
HotpatchingThis security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341.
Removal InformationFor all supported editions of SQL Server 2005:
Use Add or Remove Programs tool in Control Panel
File InformationFor GDR update of SQL Server 2008 R2:
see Microsoft Knowledge Base Article 2494088
For QFE update of SQL Server 2008 R2:
see Microsoft Knowledge Base Article 2494086

Deployment Information

Installing the Update

When you install this security update, the installer checks to see if 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.

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/?Displays the Help dialog
/quietRuns Setup in quiet mode
/reportonlyDisplays the features that this package can update
/allinstancesUpgrades all SQL Server instances and all shared components
/instancenameUpgrades a specific SQL Server instance and all shared components
/sapwdPassword for the SQL Server sa account to run scripts
/userUser account for connecting to a remote cluster node
/passwordPassword for user account for connecting to a remote cluster node
/rsupgradedatabaseaccountUser account for upgrading Reporting Services
/rsupgradepasswordPassword for user account for upgrading Reporting Services
/rsupgradedatabasePrevents the Reporting Services database from being upgraded when the parameter equals 0
/allinstancesApplies update to all instances
/InstanceName={instance}Applies update to specified instance

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. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.

Removing the Update

Example of how to remove QFE from single instance:

%windir%\SQL9_KB960090_ENU\hotfix.exe /quiet /uninstall /instancename=foo

Example of how to remove QFE from all instances:

%windir%\SQL9_KB960090_ENU\hotfix.exe /quiet /uninstall /allinstances

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 versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
    5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate 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.

Microsoft Visual Studio 2005 Service Pack 1

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 PacksNone
Deployment
Installing without user interventionVS80sp1-KB2251481-v3-X86-INTL.exe /qn
Installing without restartingVS80sp1-KB2251481-v3-X86-INTL.exe /norestart
Update log fileNot applicable
Further informationFor detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance.

For features you can selectively install, see the Office Features for Administrative Installations subsection in this section.
Restart Requirement
Restart required?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.
HotpatchingNot applicable
Removal InformationUse Add or Remove Programs tool in Control Panel.
File InformationSee Microsoft Knowledge Base Article 2251481
Registry Key VerificationHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft Visual Studio 2005 Professional Edition - ENU\KB2251481
"Installed" = dword:1

Deployment Information

Installing the Update

You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and Deployment Tools and Guidance subsection.

This security update requires that Windows Installer 2.0 or later be installed on the system. All supported versions of Windows include Windows Installer 2.0 or a later version.

To install the latest version of Windows Installer, visit the following Microsoft 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.

Supported Security Update Installation Switches
SwitchDescription
/? or /h or /helpDisplay usage dialog box.
Setup Mode 
/q[n|b|r|f]Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI
/quietSame as /q
/passiveSame as /qb
Install Options 
/extract [directory]Extract the package to the specified directory.
/uninstall or /uUninstall this update.
/addsource or /asSpecifies the source path of the product msi. This option may be used when installing the update results in a prompt to insert the installation source media for the product. For example:
<update executable> /addsource "C:\Product MSI\Visual Studio\enu\vs_setup.msi" /addsource "C:\Product MSI\Net\Netfx.msi"
Restart Options 
/norestartDo not restart after the installation is complete
/promptrestartPrompts the user for restart if necessary
/forcerestartAlways restart the computer after installation
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>
/sendreportSend installation data for this update to Microsoft as a Watson report. No personally identifiable information is sent.

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.

Removing the Update

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

Note When you remove this update, you may be prompted to insert the 2007 Microsoft Office CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.

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 “Microsoft baseline Security Analyzer” heading under the section, Microsoft Detection and Deployment Tools and Guidance.

  • File Version Verification

    Note Because there are several versions and 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 click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      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.
    5. 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.

Microsoft Visual Studio 2008 Service Pack 1

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 PacksNone
Deployment
Installing without user interventionVS90SP1-KB2251487-x86.exe /q
Installing without restartingVS90SP1-KB2251487-x86.exe /norestart
Update log fileNot applicable
Further informationFor detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance.

For features you can selectively install, see the Office Features for Administrative Installations subsection in this section.
Restart Requirement
Restart required?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.
HotpatchingNot applicable
Removal InformationUse Add or Remove Programs tool in Control Panel.
File InformationSee Microsoft Knowledge Base Article 2251487
Registry Key VerificationHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft Visual Studio Team System 2008 Team Suite - ENU\KB2251487
"ThisVersionInstalled" = REG_SZ:"Y"

Deployment Information

Installing the Update

You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and Deployment Tools and Guidance subsection.

This security update requires that Windows Installer 2.0 or later be installed on the system. All supported versions of Windows include Windows Installer 2.0 or a later version.

To install the latest version of Windows Installer, visit the following Microsoft 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.

Supported Security Update Installation Switches
SwitchDescription
/? or /h or /helpDisplay usage dialog box.
Setup Mode 
/q[n|b|r|f]Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI
/quietSame as /q
/passiveSame as /qb
Install Options 
/extract [directory]Extract the package to the specified directory.
/uninstall or /uUninstall this update.
/addsource or /asSpecifies the source path of the product msi. This option may be used when installing the update results in a prompt to insert the installation source media for the product. For example:
<update executable> /addsource "C:\Product MSI\Visual Studio\enu\vs_setup.msi" /addsource "C:\Product MSI\Net\Netfx.msi"
Restart Options 
/norestartDo not restart after the installation is complete
/promptrestartPrompts the user for restart if necessary
/forcerestartAlways restart the computer after installation
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>
/sendreportSend installation data for this update to Microsoft as a Watson report. No personally identifiable information is sent.

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.

Removing the Update

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

Note When you remove this update, you may be prompted to insert the 2007 Microsoft Office CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.

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 “Microsoft baseline Security Analyzer” heading under the section, Microsoft Detection and Deployment Tools and Guidance.

  • File Version Verification

    Note Because there are several versions and 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 click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      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.
    5. 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.

Microsoft Visual Studio 2010

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 PacksMicrosoft Visual Studio 2010 Service Pack 1
Deployment
Installing without user interventionVS10-KB2251489-x86.exe /q
Installing without restartingVS10-KB2251489-x86.exe /norestart
Update log fileNot applicable
Further informationFor detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance.

For features you can selectively install, see the Office Features for Administrative Installations subsection in this section.
Restart Requirement
Restart required?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.
HotpatchingNot applicable
Removal InformationUse Add or Remove Programs tool in Control Panel.
File InformationSee Microsoft Knowledge Base Article 2251489
Registry Key VerificationHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft Visual Studio Team System 2010 Team Suite - ENU\KB2251489
"ThisVersionInstalled" = REG_SZ:"Y"

Deployment Information

Installing the Update

You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and Deployment Tools and Guidance subsection.

This security update requires that Windows Installer 2.0 or later be installed on the system. All supported versions of Windows include Windows Installer 2.0 or a later version.

To install the latest version of Windows Installer, visit the following Microsoft 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.

Supported Security Update Installation Switches
SwitchDescription
/? or /h or /helpDisplay usage dialog box.
Setup Mode 
/q[n|b|r|f]Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI
/quietSame as /q
/passiveSame as /qb
Install Options 
/extract [directory]Extract the package to the specified directory.
/uninstall or /uUninstall this update.
/addsource or /asSpecifies the source path of the product msi. This option may be used when installing the update results in a prompt to insert the installation source media for the product. For example:
<update executable> /addsource "C:\Product MSI\Visual Studio\enu\vs_setup.msi" /addsource "C:\Product MSI\Net\Netfx.msi"
Restart Options 
/norestartDo not restart after the installation is complete
/promptrestartPrompts the user for restart if necessary
/forcerestartAlways restart the computer after installation
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>
/sendreportSend installation data for this update to Microsoft as a Watson report. No personally identifiable information is sent.

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.

Removing the Update

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

Note When you remove this update, you may be prompted to insert the 2007 Microsoft Office CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.

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 “Microsoft baseline Security Analyzer” heading under the section, Microsoft Detection and Deployment Tools and Guidance.

  • File Version Verification

    Note Because there are several versions and 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 click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      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.
    5. 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.

Other Information

Acknowledgments

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

  • Jesse Ou of Cigital for reporting the XML External Entities Resolution Vulnerability (CVE-2011-1280)

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.

Support

  • Customers in the U.S. and Canada can receive technical support from Security Support 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.
  • 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 (June 14, 2011): Bulletin published.
  • V1.1 (June 14, 2011): Removed erroneous entries from Non-Affected Software table.
  • V1.2 (June 15, 2011): Removed erroneous entry from Non-Affected Software table.
  • V1.3 (June 22, 2011): Corrected the bulletin replacement information for Microsoft InfoPath 2007 and the Systems Management Server detection information for SQL Server. This is a bulletin change only. There were no changes to the detection or security update files.
  • V2.0 (August 9, 2011): Bulletin rereleased to announce a detection change to the update for Microsoft Visual Studio 2005 Service Pack 1 (KB2251481) to add detection for related software listed in the update FAQ. There were no changes to the security update files. Customers who have already successfully updated their systems do not need to reinstall this update.
  • V2.1 (September 13, 2011): Added an update FAQ to announce a detection change for KB2494089 that corrects an installation issue. This is a detection change only. There were no changes to the security update files. Customers who have already successfully updated their systems do not need to take any action.
  • V2.2 (January 18, 2012): Added a note to the Affected and Non-Affected Software section to clarify that this update also applies to 32-bit and x64-based SQL Server 2008 and SQL Server 2008 R2 Express and Express Advanced editions.
  • V2.3 (January 24, 2012): Added an entry to the update FAQ to announce a detection change for KB2251481, KB2251487, and KB2251489 to correct an installation issue. This is a detection change only. There were no changes to the security update files. Customers who have already successfully updated their systems do not need to take any action.
  • V2.4 (February 15, 2012): Corrected the SQL Server Version Range for SQL Server 2008 R2 in the update FAQ.

Built at 2014-04-16T02:39:51Z-07:00

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.