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

Microsoft Security Bulletin MS12-070 - Important

Vulnerability in SQL Server Could Allow Elevation of Privilege

Published: October 09, 2012

Version: 1.0

General Information

Executive Summary

This security update resolves a privately reported vulnerability in Microsoft SQL Server on systems running SQL Server Reporting Services (SSRS). The vulnerability is a cross-site-scripting (XSS) vulnerability that could allow elevation of privilege, enabling an attacker to execute arbitrary commands on the SSRS site in the context of the targeted user. An attacker could exploit this vulnerability by sending a specially crafted link to the user and convincing the user to click the link. An attacker could also host a website that contains a webpage designed to exploit the vulnerability. In addition, compromised websites and websites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability.

This security update is rated Important for Microsoft SQL Server 2000 Reporting Services Service Pack 2 and for systems running SQL Server Reporting Services (SSRS) on Microsoft SQL Server 2005 Service Pack 4, Microsoft SQL Server 2008 Service Pack 2, Microsoft SQL Server 2008 Service Pack 3, Microsoft SQL Server 2008 R2 Service Pack 1, and Microsoft SQL Server 2012. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerability by correcting the way that SQL Server Report Manager validates input parameters. 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 2754849 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, see Microsoft Support Lifecycle.

Microsoft SQL Server

Depending on your software version or edition, you may need to choose between GDR and QFE software update links below in order to manually install your update from the Microsoft Download Center. For more information on determining which update to install on your system, see the Frequently Asked Questions (FAQ) Related to This Security Update subsection, in this section.

GDR Software UpdatesQFE Software UpdatesMaximum Security ImpactAggregate Severity RatingUpdates Replaced
SQL Server 2000
Not applicableMicrosoft SQL Server 2000 Reporting Services Service Pack 2
(KB983814)
Elevation of PrivilegeImportantKB970899 in MS09-062 replaced by KB983814
SQL Server 2005
Microsoft SQL Server 2005 Express Edition with Advanced Services Service Pack 4[1]
(KB2716429)
Microsoft SQL Server 2005 Express Edition with Advanced Services Service Pack 4[1]
(KB2716427)
Elevation of PrivilegeImportantKB2494120 and KB2546869 in MS11-049 replaced by KB2716429

KB2494123 in MS11-049 replaced by KB2716427
Microsoft SQL Server 2005 for 32-bit Systems Service Pack 4[1]
(KB2716429)
Microsoft SQL Server 2005 for 32-bit Systems Service Pack 4[1]
(KB2716427)
Elevation of PrivilegeImportantKB2494120 and KB2546869 in MS11-049 replaced by KB2716429

KB2494123 in MS11-049 replaced by KB2716427
Microsoft SQL Server 2005 for x64-based Systems Service Pack 4[1]
(KB2716429)
Microsoft SQL Server 2005 for x64-based Systems Service Pack 4 [1]
(KB2716427)
Elevation of PrivilegeImportantKB2494120 and KB2546869 in MS11-049 replaced by KB2716429

KB2494123 in MS11-049 replaced by KB2716427
Microsoft SQL Server 2005 for Itanium-based Systems Service Pack 4[1]
(KB2716429)
Microsoft SQL Server 2005 for Itanium-based Systems Service Pack 4[1]
(KB2716427)
Elevation of PrivilegeImportantKB2494120 and KB2546869 in MS11-049 replaced by KB2716429

KB2494123 in MS11-049 replaced by KB2716427
SQL Server 2008
Microsoft SQL Server 2008 for 32-bit Systems Service Pack 2[1]
(KB2716434)
Microsoft SQL Server 2008 for 32-bit Systems Service Pack 2[1]
(KB2716433)
Elevation of PrivilegeImportantKB2494089 in MS11-049 replaced by KB2716434

KB2494094 in MS11-049 replaced by KB2716433
Microsoft SQL Server 2008 for 32-bit Systems Service Pack 3[1]
(KB2716436)
Microsoft SQL Server 2008 for 32-bit Systems Service Pack 3[1]
(KB2716435)
Elevation of PrivilegeImportantNone
Microsoft SQL Server 2008 for x64-based Systems Service Pack 2[1]
(KB2716434)
Microsoft SQL Server 2008 for x64-based Systems Service Pack 2[1]
(KB2716433)
Elevation of PrivilegeImportantKB2494089 in MS11-049 replaced by KB2716434

KB2494094 in MS11-049 replaced by KB2716433
Microsoft SQL Server 2008 for x64-based Systems Service Pack 3[1]
(KB2716436)
Microsoft SQL Server 2008 for x64-based Systems Service Pack 3[1]
(KB2716435)
Elevation of PrivilegeImportantNone
Microsoft SQL Server 2008 for Itanium-based Systems Service Pack 2[1]
(KB2716434)
Microsoft SQL Server 2008 for Itanium-based Systems Service Pack 2[1]
(KB2716433)
Elevation of PrivilegeImportantKB2494089 in MS11-049 replaced by KB2716434

KB2494094 in MS11-049 replaced by KB2716433
Microsoft SQL Server 2008 for Itanium-based Systems Service Pack 3[1]
(KB2716436)
Microsoft SQL Server 2008 for Itanium-based Systems Service Pack 3[1]
(KB2716435)
Elevation of PrivilegeImportantNone
SQL Server 2008 R2
Microsoft SQL Server 2008 R2 for 32-bit Systems Service Pack 1[1]
(KB2716440)
Microsoft SQL Server 2008 R2 for 32-bit Systems Service Pack 1[1]
(KB2716439)
Elevation of PrivilegeImportantNone
Microsoft SQL Server 2008 R2 for x64-based Systems Service Pack 1[1]
(KB2716440)
Microsoft SQL Server 2008 R2 for x64-based Systems Service Pack 1[1]
(KB2716439)
Elevation of PrivilegeImportantNone
Microsoft SQL Server 2008 R2 for Itanium-based Systems Service Pack 1[1]
(KB2716440)
Microsoft SQL Server 2008 R2 for Itanium-based Systems Service Pack 1[1]
(KB2716439)
Elevation of PrivilegeImportantNone
SQL Server 2012
Microsoft SQL Server 2012 for 32-bit Systems[1]
(KB2716442)
Microsoft SQL Server 2012 for 32-bit Systems[1]
(KB2716441)
Elevation of PrivilegeImportantNone
Microsoft SQL Server 2012 for x64-based Systems[1]
(KB2716442)*
Microsoft SQL Server 2012 for x64-based Systems[1]
(KB2716441)
Elevation of PrivilegeImportantNone

[1]This update is only offered to customers running SQL Server Reporting Services (SSRS).

Non-Affected Software

Microsoft SQL Server Software
Microsoft SQL Server 2000 Service Pack 4
Microsoft SQL Server 2000 Itanium Edition Service Pack 4
Microsoft SQL Server 2000 Analysis Services Service Pack 4
Microsoft SQL Server 2000 Desktop Engine (MSDE) on Microsoft Windows Server 2003 Service Pack 2
Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) Service Pack 4
Microsoft SQL Server 2005 Express Edition Service Pack 4
Microsoft SQL Server Management Studio Express (SSMSE) 2005
Microsoft SQL Server 2008 R2 for 32-bit Systems Service Pack 2
Microsoft SQL Server 2008 R2 for x64-based Systems Service Pack 2
Microsoft SQL Server 2008 R2 for Itanium-based Systems Service Pack 2
Microsoft Data Engine (MSDE) 1.0
Microsoft Data Engine (MSDE) 1.0 Service Pack 4
Microsoft Data Engine 1.0

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.

Where are the hashes of the security updates? 
The SHA1 and SHA2 hashes of the security updates can be used to verify the authenticity of downloaded security update packages. For the hash information pertaining to this update, see Microsoft Knowledge Base Article 2754849.

There are GDR and/or 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 2000:

SQL Server Version Range
8.0.1038.0-8.0.1076.0
SQL Server Update
Not applicableMicrosoft SQL Server 2000 Reporting Services Service Pack 2
(KB983814)

For SQL Server 2005:

SQL Server Version Range
9.0.5000-9.0.50689.0.5200-9.0.5323
SQL Server Update
SQL Server 2005 Service Pack 4 GDR
(KB2716429)
SQL Server 2005 Service Pack 4 QFE
(KB2716427)

For SQL Server 2008:

SQL Server Version Range
10.00.4000-10.00.406610.00.4260-10.00.437010.00.5500-10.00.551110.00.5750-10.00.5825
SQL Server Update
SQL Server 2008 Service Pack 2 GDR
(KB2716434)
SQL Server 2005 Service Pack 2 QFE
(KB2716433)
SQL Server 2008 Service Pack 3 GDR
(KB2716436)
SQL Server 2005 Service Pack 3 QFE
(KB2716435)

For SQL Server 2008 R2:

SQL Server Version Range
10. 50.2500-10.50.254910.50.2750- 10.50.2860
SQL Server Update
SQL Server 2008 R2 Service Pack 1 GDR
(KB2716440)
SQL Server 2008 R2 Service Pack 1 QFE
(KB2716439)

For SQL Server 2012:

SQL Server Version Range
11.0.2100- 11.0.221711.0.2300-11.0.2375
SQL Server Update
SQL Server 2012GDR
(KB2716442)
SQL Server 2012 QFE
(KB2716441)

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

Will the update be offered to SQL Server clusters? 
Yes. The update will also be offered to SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 instances that are clustered. Updates for SQL Server clusters will require user interaction. SQL Server 2000 Reporting Services does not support SQL Server clusters.

If the SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, or SQL Server 2012 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.

The reference tables for SQL Server 2000 Reporting Services in the Security Update Information section show that some updates may require a restart. How can I tell if my update will require a restart? 
For SQL Server 2000 Reporting Services, it is possible to have dependent services. Dependent services are not restarted after the service they are dependent on is stopped and restarted. For this reason, a restart should be performed after a successful install to ensure that dependent services are started. For more information on determining whether you are running dependent services, see Microsoft Knowledge Base Article 953741.

Will the updates be applied to disabled instances of SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012? 
No. Only those instances of SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012 that do not have a Startup type of disabled will be updated by the installer. For more information on disabled services, see Microsoft Knowledge Base Article 953740.

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, see the Microsoft Support Lifecycle website.

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 Service Pack Lifecycle Support Policy.

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, see the Microsoft Worldwide Information website, 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 October bulletin summary. For more information, see Microsoft Exploitability Index.

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected SoftwareReflected XSS Vulnerability - CVE-2012-2552Aggregate Severity Rating
SQL Server 2000
Microsoft SQL Server 2000 Reporting Services Service Pack 2Important 
Elevation of Privilege
Important
SQL Server 2005
Microsoft SQL Server 2005 Express Edition with Advanced Services Service Pack 4Important 
Elevation of Privilege
Important
Microsoft SQL Server 2005 for 32-bit Systems Service Pack 4Important 
Elevation of Privilege
Important
Microsoft SQL Server 2005 for x64-based Systems Service Pack 4Important 
Elevation of Privilege
Important
Microsoft SQL Server 2005 for Itanium-Based Systems Service Pack 4Important 
Elevation of Privilege
Important
SQL Server 2008
Microsoft SQL Server 2008 for 32-bit Systems Service Pack 2Important 
Elevation of Privilege
Important
Microsoft SQL Server 2008 for 32-bit Systems Service Pack 3Important 
Elevation of Privilege
Important
Microsoft SQL Server 2008 for x64-based Systems Service Pack 2Important 
Elevation of Privilege
Important
Microsoft SQL Server 2008 for x64-based Systems Service Pack 3Important 
Elevation of Privilege
Important
Microsoft SQL Server 2008 for Itanium-Based Systems Service Pack 2Important 
Elevation of Privilege
Important
Microsoft SQL Server 2008 for Itanium-Based Systems Service Pack 3Important 
Elevation of Privilege
Important
SQL Server 2008 R2
Microsoft SQL Server 2008 R2 for 32-bit Systems Service Pack 1Important 
Elevation of Privilege
Important
Microsoft SQL Server 2008 R2 for Itanium-Based Systems Service Pack 1Important 
Elevation of Privilege
Important
Microsoft SQL Server 2008 R2 for x64-based Systems Service Pack 1Important 
Elevation of Privilege
Important
SQL Server 2012
Microsoft SQL Server 2012 for 32-bit SystemsImportant 
Elevation of Privilege
Important
Microsoft SQL Server 2012 for x64-based SystemsImportant 
Elevation of Privilege
Important

A reflected XSS vulnerability exists in SQL Server Report Manager that could allow an attacker to inject a client-side script into the user's instance of Internet Explorer. The script could spoof content, disclose information, or take any action that the user could take on the site on behalf of the targeted user.

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

Mitigating Factors for Reflected XSS Vulnerability - CVE-2012-2552

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 website that contains a webpage that is used to exploit this vulnerability. In addition, compromised websites and websites 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 websites. Instead, an attacker would have to convince users to visit the website, typically by getting them to click a link in an email message or Instant Messenger message that takes them to the attacker's website.
  • The XSS Filter in Internet Explorer 8, Internet Explorer 9, and Internet Explorer 10 prevents this attack for Internet Explorer 8, Internet Explorer 9, and Internet Explorer 10 users when browsing to websites in the Internet Zone. Note that the XSS Filter in Internet Explorer 8, Internet Explorer 9, and Internet Explorer 10 is enabled by default in the Internet zone, but is not enabled by default in the Intranet Zone.

Workarounds for Reflected XSS Vulnerability - CVE-2012-2552

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:

  • Enable Internet Explorer 8, Internet Explorer 9, and Internet Explorer 10 XSS filter for Intranet Zone

    You can help protect against exploitation of this vulnerability by changing your settings to enable the XSS filter in the Local intranet security zone. (XSS filter is enabled by default in the Internet security zone.) To do this, perform the following steps:

    1. In Internet Explorer 8, Internet Explorer 9, or Internet Explorer 10, click Internet Options on the Tools menu.
    2. Click the Security tab.
    3. Click Local intranet, and then click Custom level.
    4. Under Settings, in the Scripting section, under Enable XSS filter, click Enable, and then click OK.
    5. Click OK two times to return to Internet Explorer.

    Impact of workaround. Internal sites not previously flagged as being XSS risks could be flagged.

    How to undo the workaround.

    To undo this workaround, perform the following steps.

    1. In Internet Explorer 8, Internet Explorer 9, or Internet Explorer 10, click Internet Options on the Tools menu.
    2. Click the Security tab.
    3. Click Local intranet, and then click Custom level.
    4. Under Settings, in the Scripting section, under Enable XSS filter, click Disable, and then click OK.
    5. Click OK two times to return to Internet Explorer.

FAQ for Reflected XSS Vulnerability - CVE-2012-2552

What is the scope of the vulnerability? 
This is a reflected XSS vulnerability that could allow elevation of privilege.

What causes the vulnerability? 
The vulnerability is caused when the SQL Server Report Manager does not properly validate a request parameter on the Report Manager SQL Server site.

What is cross-site scripting (XSS)? 
Cross-site scripting (XSS) is a class of security vulnerability that can enable an attacker to inject script into the response to a webpage request. This script is then run by the requesting application, often times a web browser. The script could then spoof content, disclose information, or take any action that the user could take on the affected website, on behalf of the targeted user.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could inject a client-side script into the user's instance of Internet Explorer. The script could spoof content, disclose information, or take any action that the user could take on the site on behalf of the targeted user.

How could an attacker exploit the vulnerability? 
An attacker could exploit the vulnerability by sending a specially crafted link to the user and convincing the user to click the link. An attacker could also host a website that contains a webpage designed to exploit this vulnerability. In addition, compromised websites and websites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability.

What systems are primarily at risk from the vulnerability? 
Servers running affected editions of Microsoft SQL Server are primarily at risk. SQL Server systems that do not have SQL Server Reporting Services installed are not at risk of this vulnerability and will not be offered the update.

What does the update do? 
The update addresses the vulnerability by correcting the way that SQL Server Report Manager encodes input parameters.

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 website 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, "MS12-001"), you can add all 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) lets administrators scan local and remote systems for missing security updates as well as common security misconfigurations. For more information, see Microsoft Baseline Security Analyzer.

The following table provides the MBSA detection summary for this security update.

Software MBSA
Microsoft SQL Server 2000 Reporting Services Service Pack 2Yes
Microsoft SQL Server 2005 Express Edition with Advanced Services Service Pack 4Yes
Microsoft SQL Server 2005 for 32-bit Systems Service Pack 4Yes
Microsoft SQL Server 2005 for x64-based Systems Service Pack 4Yes
Microsoft SQL Server 2005 for Itanium-Based Systems Service Pack 4Yes
Microsoft SQL Server 2008 for 32-bit Systems Service Pack 2Yes
Microsoft SQL Server 2008 for 32-bit Systems Service Pack 3Yes
Microsoft SQL Server 2008 for x64-based Systems Service Pack 2Yes
Microsoft SQL Server 2008 for x64-based Systems Service Pack 3Yes
Microsoft SQL Server 2008 for Itanium-Based Systems Service Pack 2Yes
Microsoft SQL Server 2008 for Itanium-Based Systems Service Pack 3Yes
Microsoft SQL Server 2008 R2 for 32-bit Systems Service Pack 1Yes
Microsoft SQL Server 2008 R2 for x64-based Systems Service Pack 1Yes
Microsoft SQL Server 2008 R2 for Itanium-Based Systems Service Pack 1Yes
Microsoft SQL Server 2012 for 32-bit SystemsYes
Microsoft SQL Server 2012 for x64-based SystemsYes

Note For customers using legacy software not supported by the latest release of MBSA, Microsoft Update, and Windows Server Update Services, please see 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 ITMUSystem Center Configuration Manager
Microsoft SQL Server 2000 Reporting Services Service Pack 2YesYes
Microsoft SQL Server 2005 Express Edition with Advanced Services Service Pack 4YesYes
Microsoft SQL Server 2005 for 32-bit Systems Service Pack 4YesYes
Microsoft SQL Server 2005 for x64-based Systems Service Pack 4YesYes
Microsoft SQL Server 2005 for Itanium-Based Systems Service Pack 4YesYes
Microsoft SQL Server 2008 for 32-bit Systems Service Pack 2YesYes
Microsoft SQL Server 2008 for 32-bit Systems Service Pack 3YesYes
Microsoft SQL Server 2008 for x64-based Systems Service Pack 2YesYes
Microsoft SQL Server 2008 for x64-based Systems Service Pack 3YesYes
Microsoft SQL Server 2008 for Itanium-Based Systems Service Pack 2YesYes
Microsoft SQL Server 2008 for Itanium-Based Systems Service Pack 3YesYes
Microsoft SQL Server 2008 R2 for 32-bit Systems Service Pack 1YesYes
Microsoft SQL Server 2008 R2 for x64-based Systems Service Pack 1YesYes
Microsoft SQL Server 2008 R2 for Itanium-Based Systems Service Pack 1YesYes
Microsoft SQL Server 2012 for 32-bit SystemsYesYes
Microsoft SQL Server 2012 for x64-based SystemsYesYes

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. 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 uses WSUS 3.0 for detection of updates. For more information, see System Center.

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

SQL Server 2000 Reporting Services

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 PacksNo future service packs are planned
Deployment
Installing without user interventionFor SQL Server 2000 Reporting Services Service Pack 2:
SQL2000.RS-KB983814-v8.00.1077.00-ENG.exe /quiet
Installing without restartingFor SQL Server 2000 Reporting Services Service Pack 2:
SQL2000.RS-KB983814-v8.00.1077.00-ENG.exe /norestart
Installing a single instanceFor SQL Server 2000 Reporting Services Service Pack 2:
SQL2000.RS-KB983814-v8.00.1077.00-ENG.exe /quiet /InstanceName={instance}
Update log fileSQL2000.RS-KB983814-v8.00.1077.00-<language>.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart requiredFor SQL Server 2000 Reporting Services Service Pack 2:

A restart is recommended after the update installation to restart any dependent services. For additional information, please see "How can I tell if my update will require a restart?" in the Update FAQ section of this bulletin. If a restart is required, the installer will prompt or return exit code 3010.
HotPatchingNot applicable
Removal InformationUse Add or Remove Programs item in Control Panel.
File InformationSee Microsoft Knowledge Base Article 983814

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
/helpDisplays the command-line options
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed
/forcerestartRestarts 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.
/promptrestartDisplay a dialog box prompting the local user to allow a restart
Special Options
/overwriteoemOverwrites OEM files without prompting
/nobackupDoes not back up files needed for uninstall
/forceappscloseForces other programs to close when the computer shuts down
/log:pathAllows the redirection of installation log files
/integrate:pathIntegrates the update into the Windows source files. These files are located at the path that is specified in the switch.

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

Use Add or Remove Programs in Control Panel.

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

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 PacksNo future service packs are planned
Deployment
Installing without user interventionFor GDR update of SQL Server 2005 Express Edition with Advanced Services Service Pack 4:
SQLServer2005-KB2716429-x86-ENU.exe /quiet /allinstances
For GDR update of SQL Server 2005 for 32-bit Systems Service Pack 4:
SQLServer2005-KB2716429-x86-ENU.exe /quiet /allinstances
For GDR update of SQL Server 2005 for x64-based Systems Service Pack 4:
SQLServer2005-KB2716429-x64-ENU.exe /quiet /allinstances
For GDR update of SQL Server 2005 for Itanium-based Systems Service Pack 4:
SQLServer2005-KB2716429-IA64-ENU.exe /quiet /allinstances
For QFE update of SQL Server 2005 Express Edition with Advanced Services Service Pack 4:
SQLServer2005-KB2716427-x86-ENU.exe /quiet /allinstances
For QFE update of SQL Server 2005 for 32-bit Systems Service Pack 4:
SQLServer2005-KB2716427-x86-ENU.exe /quiet /allinstances
For QFE update of SQL Server 2005 for x64-based Systems Service Pack 4:
SQLServer2005-KB2716427-x64-ENU.exe /quiet /allinstances
For QFE update of SQL Server 2005 for Itanium-based Systems Service Pack 4:
SQLServer2005-KB2716427-IA64-ENU.exe /quiet /allinstances
Installing a single instanceFor GDR update of SQL Server 2005 Express Edition with Advanced Services Service Pack 4:
SQLServer2005-KB2716429-x86-ENU.exe /quiet /InstanceName={instance}
For GDR update of SQL Server 2005 for 32-bit Systems Service Pack 4:
SQLServer2005-KB2716429-x86-ENU.exe /quiet /InstanceName={instance}
For GDR update of SQL Server 2005 for x64-based Systems Service Pack 4:
SQLServer2005-KB2716429-x64-ENU.exe /quiet /InstanceName={instance}
For GDR update of SQL Server 2005 for Itanium-based Systems Service Pack 4:
SQLServer2005-KB2716429-IA64-ENU.exe /quiet /InstanceName={instance}
For QFE update of SQL Server 2005 Express Edition with Advanced Services Service Pack 4:
SQLServer2005-KB2716427-x86-ENU.exe /quiet /InstanceName={instance}
For QFE update of SQL Server 2005 for 32-bit Systems Service Pack 4:
SQLServer2005-KB2716427-x86-ENU.exe /quiet /InstanceName={instance}
For QFE update of SQL Server 2005 for x64-based Systems Service Pack 4:
SQLServer2005-KB2716427-x64-ENU.exe /quiet /InstanceName={instance}
For QFE update of SQL Server 2005 for Itanium-based Systems Service Pack 4:
SQLServer2005-KB2716427-IA64-ENU.exe /quiet /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 except SQL Server 2005 for x64-based Systems Service Pack 4:
Use Add or Remove Programs in Control Panel

Note There is an uninstall issue with SQL Server 2005 for x64-based Systems Service Pack 4. See Microsoft Knowledge Base Article 2754849 for more information.
File InformationFor GDR update of SQL Server 2005 Service Pack 4:
See Microsoft Knowledge Base Article 2716429
For QFE update of SQL Server 2005 Service Pack 4:
See Microsoft Knowledge Base Article 2716427

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.

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 4
Deployment
Installing without user interventionFor GDR update of SQL Server 2008 for 32-bit Systems Service Pack 2:
SQLServer2008-KB2716434-x86.exe /quiet /allinstances
For GDR update of SQL Server 2008 for x64-based Systems Service Pack 2:
SQLServer2008-KB2716434-x64.exe /quiet /allinstances
For GDR update of SQL Server 2008 for Itanium-based Systems Service Pack 2:
SQLServer2008-KB2716434-IA64.exe /quiet /allinstances
For QFE update of SQL Server 2008 for 32-bit Systems Service Pack 2:
SQLServer2008-KB2716433-x86.exe /quiet /allinstances
For QFE update of SQL Server 2008 for x64-based Systems Service Pack 2:
SQLServer2008-KB2716433-x64.exe /quiet /allinstances
For QFE update of SQL Server 2008 for Itanium-based Systems Service Pack 2:
SQLServer2008-KB2716433-IA64.exe /quiet /allinstances
For GDR update of SQL Server 2008 for 32-bit Systems Service Pack 3:
SQLServer2008-KB2716436-x86.exe /quiet /allinstances
For GDR update of SQL Server 2008 for x64-based Systems Service Pack 3:
SQLServer2008-KB2716436-x64.exe /quiet /allinstances
For GDR update of SQL Server 2008 for Itanium-based Systems Service Pack 3:
SQLServer2008-KB2716436-IA64.exe /quiet /allinstances
For QFE update of SQL Server 2008 for 32-bit Systems Service Pack 3:
SQLServer2008-KB2716435-x86.exe /quiet /allinstances
For QFE update of SQL Server 2008 for x64-based Systems Service Pack 3:
SQLServer2008-KB2716435-x64.exe /quiet /allinstances
For QFE update of SQL Server 2008 for Itanium-based Systems Service Pack 3:
SQLServer2008-KB2716435-IA64.exe /quiet /allinstances
Installing a single instanceFor GDR update of SQL Server 2008 for 32-bit Systems Service Pack 2:
SQLServer2008-KB2716434-x86.exe /quiet /InstanceName={instance}
For GDR update of SQL Server 2008 for x64-based Systems Service Pack 2:
SQLServer2008-KB2716434-x64.exe /quiet /InstanceName={instance}
For GDR update of SQL Server 2008 for Itanium-based Systems Service Pack 2:
SQLServer2008-KB2716434-IA64.exe /quiet /InstanceName={instance}
For QFE update of SQL Server 2008 for 32-bit Systems Service Pack 2:
SQLServer2008-KB2716433-x86.exe /quiet /InstanceName={instance}
For QFE update of SQL Server 2008 for x64-based Systems Service Pack 2:
SQLServer2008-KB2716433-x64.exe /quiet /InstanceName={instance}
For QFE update of SQL Server 2008 for Itanium-based Systems Service Pack 2:
SQLServer2008-KB2716433-IA64.exe /quiet /InstanceName={instance}
For GDR update of SQL Server 2008 for 32-bit Systems Service Pack 3:
SQLServer2008-KB2716436-x86.exe /quiet /InstanceName={instance}
For GDR update of SQL Server 2008 for x64-based Systems Service Pack 3:
SQLServer2008-KB2716436-x64.exe /quiet /InstanceName={instance}
For GDR update of SQL Server 2008 for Itanium-based Systems Service Pack 3:
SQLServer2008-KB2716436-IA64.exe /quiet /InstanceName={instance}
For QFE update of SQL Server 2008 Service Pack 3:
SQLServer2008-KB2716435-x86.exe /quiet /InstanceName={instance}
For QFE update of SQL Server 2008 for x64-based Systems Service Pack 3:
SQLServer2008-KB2716435-x64.exe /quiet /InstanceName={instance}
For QFE update of SQL Server 2008 for Itanium-based Systems Service Pack 3:
SQLServer2008-KB2716435-IA64.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.

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 2008:
Use Add or Remove Programs in Control Panel
File InformationFor GDR update of SQL Server 2008 Service Pack 2:
see Microsoft Knowledge Base Article 2716434
For QFE update of SQL Server 2008 Service Pack 2:
see Microsoft Knowledge Base Article 2716433
For GDR update of SQL Server 2008 Service Pack 3:
see Microsoft Knowledge Base Article 2716436
For QFE update of SQL Server 2008 Service Pack 3:
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.

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 2
Deployment
Installing without user interventionFor GDR update of SQL Server 2008 R2 for 32-bit Systems Service Pack 1:
SQLServer2008R2-KB2716440-x86.exe /quiet /allinstances
For GDR update of SQL Server 2008 R2 for x64-based Systems Service Pack 1:
SQLServer2008R2-KB2716440-x64.exe /quiet /allinstances
For GDR update of SQL Server 2008 R2 for Itanium-based Systems Service Pack 1:
SQLServer2008R2-KB2716440-IA64.exe /quiet /allinstances
For QFE update of SQL Server 2008 R2 for 32-bit Systems Service Pack 1:
SQLServer2008R2-KB2716439-x86.exe /quiet /allinstances
For QFE update of SQL Server 2008 R2 for x64-based Systems Service Pack 1:
SQLServer2008R2-KB2716439-x64.exe /quiet /allinstances
For QFE update of SQL Server 2008 R2 for Itanium-based Systems Service Pack 1:
SQLServer2008R2-KB2716439-IA64.exe /quiet /allinstances
Installing a single instanceFor GDR update of SQL Server 2008 R2 for 32-bit Systems Service Pack 1:
SQLServer2008R2-KB2716440-x86.exe /quiet /InstanceName={instance}
For GDR update of SQL Server 2008 R2 for x64-based Systems Service Pack 1:
SQLServer2008R2-KB2716440-x64.exe /quiet /InstanceName={instance}
For GDR update of SQL Server 2008 R2 for Itanium-based Systems Service Pack 1:
SQLServer2008R2-KB2716440-IA64.exe /quiet /InstanceName={instance}
For QFE update of SQL Server 2008 R2 for 32-bit Systems Service Pack 1:
SQLServer2008R2-KB2716439-x86.exe /quiet /InstanceName={instance}
For QFE update of SQL Server 2008 R2 for x64-based Systems Service Pack 1:
SQLServer2008R2-KB2716439-x64.exe /quiet /InstanceName={instance}
For QFE update of SQL Server 2008 R2 for Itanium-based Systems Service Pack 1:
SQLServer2008R2-KB2716439-IA64.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 R2 instances that are clustered.

If your SQL Server 2008 R2 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 2008 R2:
Use Add or Remove Programs in Control Panel
File InformationFor GDR update of SQL Server 2008 R2 Service Pack 1:
see Microsoft Knowledge Base Article 2716440
For QFE update of SQL Server 2008 R2 Service Pack 1:
see Microsoft Knowledge Base Article 2716439

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.

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 2012

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 2012 Service Pack 1
Deployment
Installing without user interventionFor GDR update of SQL Server 2012 for 32-bit Systems:
SQLServer2012-KB2716442-x86.exe /quiet /allinstances
For GDR update of SQL Server 2012 for x64-based Systems:
SQLServer2012-KB2716442-x64.exe /quiet /allinstances
For QFE update of SQL Server 2012 for 32-bit Systems:
SQLServer2012-KB2716441-x86.exe /quiet /allinstances
For QFE update of SQL Server 2012 for x64-based Systems:
SQLServer2012-KB2716441-x64.exe /quiet /allinstances
Installing a single instanceFor GDR update of SQL Server 2012 for 32-bit Systems:
SQLServer2012-KB2716442-x86.exe /quiet /InstanceName={instance}
For GDR update of SQL Server 2012 for x64-based Systems:
SQLServer2012-KB2716442-x64.exe /quiet /InstanceName={instance}
For QFE update of SQL Server 2012 for 32-bit Systems:
SQLServer2012-KB2716441-x86.exe /quiet /InstanceName={instance}
For QFE update of SQL Server 2012 for x64-based Systems:
SQLServer2012-KB2716441-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 2012 instances that are clustered.

If your SQL Server 2012 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 2008 R2:
Use Add or Remove Programs in Control Panel
File InformationFor GDR update of SQL Server 2012:
see Microsoft Knowledge Base Article 2716442
For QFE update of SQL Server 2012:
see Microsoft Knowledge Base Article 2716441

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.

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.

Other Information

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 go to the active protections websites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.

Support

How to obtain help and support for this security update

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 (October 9, 2012): Bulletin published.

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.