Export (0) Print
Expand All

Microsoft Security Bulletin MS08-040 - Important

Vulnerabilities in Microsoft SQL Server Could Allow Elevation of Privilege (941203)

Published: July 08, 2008 | Updated: March 18, 2009

Version: 1.9

General Information

Executive Summary

This security update resolves four privately disclosed vulnerabilities. The more serious of the vulnerabilities could allow an attacker to run code and to take complete control of an affected system. An authenticated attacker could then install programs; view, change, or delete data; or create new accounts with full administrative rights.

This security update is rated Important for supported releases of SQL Server 7.0, SQL Server 2000, SQL Server 2005, Microsoft Data Engine (MSDE) 1.0, Microsoft SQL Server 2000 Desktop Engine (MSDE 2000), Microsoft SQL Server 2005 Express Edition, Microsoft SQL Server 2000 Desktop Engine (WMSDE), and Windows Internal Database (WYukon). For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerabilities by modifying the way that SQL Server manages page reuse, allocating more memory for the convert function, validating on-disk files before loading them, and validating insert statements. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.

Recommendation. Microsoft recommends that customers apply the update at the earliest opportunity.

Known Issues. Microsoft Knowledge Base Article 941203 documents the currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues. For more information about installing these updates, see the Frequently Asked Questions (FAQ) Related to This Security Update subsection, in this section.

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.

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.

Affected Software

SQL Server

GDR Software UpdatesQFE Software UpdatesMaximum Security ImpactAggregate Severity RatingBulletins Replaced by this Update
SQL Server 7.0 Service Pack 4
(KB948113)
SQL Server 7.0 Service Pack 4
(KB948113)
Elevation of PrivilegeImportantNone
SQL Server 2000 Service Pack 4
(KB948110)
SQL Server 2000 Service Pack 4
(KB948111)
Elevation of PrivilegeImportantNone
SQL Server 2000 Itanium-based Edition Service Pack 4
(KB948110)
SQL Server 2000 Itanium-based Edition Service Pack 4
(KB948111)
Elevation of PrivilegeImportantNone
SQL Server 2005 Service Pack 2
(KB948109)
SQL Server 2005 Service Pack 2
(KB948108)
Elevation of PrivilegeImportantNone
SQL Server 2005 x64 Edition Service Pack 2
(KB948109)
SQL Server 2005 x64 Edition Service Pack 2
(KB948108)
Elevation of PrivilegeImportantNone
SQL Server 2005 with SP2 for Itanium-based Systems
(KB948109)
SQL Server 2005 with SP2 for Itanium-based Systems
(KB948108)
Elevation of PrivilegeImportantNone
Microsoft Data Engine (MSDE) 1.0 Service Pack 4
(KB948113)
Microsoft Data Engine (MSDE) 1.0 Service Pack 4
(KB948113)
Elevation of PrivilegeImportantNone
Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) Service Pack 4
(KB948110)
Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) Service Pack 4
(KB948111)
Elevation of PrivilegeImportantNone
Microsoft SQL Server 2005 Express Edition Service Pack 2
(KB948109)
Microsoft SQL Server 2005 Express Edition Service Pack 2
(KB948108)
Elevation of PrivilegeImportantNone
Microsoft SQL Server 2005 Express Edition with Advanced Services Service Pack 2
(KB948109)
Microsoft SQL Server 2005 Express Edition with Advanced Services Service Pack 2
(KB948108)
Elevation of PrivilegeImportantNone

Windows Components

Operating SystemComponentMaximum Security ImpactAggregate Severity RatingBulletins Replaced by this Update
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 Microsoft SQL Server 2000 Desktop Engine (WMSDE)
(KB948110)
Elevation of PrivilegeImportantNone
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 Windows Internal Database (WYukon) Service Pack 2
(KB948109)
Elevation of PrivilegeImportantNone
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 Microsoft SQL Server 2000 Desktop Engine (WMSDE)
(KB948110)
Elevation of PrivilegeImportantNone
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 Windows Internal Database (WYukon) x64 Edition Service Pack 2
(KB948109)
Elevation of PrivilegeImportantNone
Windows Server 2008 for 32-bit Systems* Windows Internal Database (WYukon) Service Pack 2
(KB948109)
Elevation of PrivilegeImportantNone
Windows Server 2008 for x64-based Systems* Windows Internal Database (WYukon) x64 Edition Service Pack 2
(KB948109)
Elevation of PrivilegeImportantNone

*Windows Server 2008 server core installation affected. For supported editions of Windows Server 2008, this update applies, with the same severity rating, whether or not Windows Server 2008 was installed using the Server Core installation option. For more information on this installation option, see Server Core. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see Compare Server Core Installation Options.

Non-Affected Software

SoftwareComponent
Application Center 2000 Service Pack 2Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) Service Pack 3a

Why was this bulletin revised on August 12, 2008? 
Microsoft revised this bulletin to communicate a change in the installation code for the security update for SQL Server 2005 Service Pack 2 to address an installation issue. This is an installation code change only. There were no changes to the security update binaries. Although WSUS administrators will see this as a new revision to the update, customers who have already successfully installed the security update will not need to reinstall the update.

Why was this bulletin revised on July 23, 2008? 
This bulletin was revised to add removal information notes for Microsoft SQL Server 2000 Desktop Engine (WMSDE) and Windows Internal Database (WYukon) clarifying that removal of this security update for WMSDE or WYukon will also completely remove the instance of WMSDE or WYukon from the system.

Why was this bulletin revised on July 18, 2008? 
This bulletin was revised to communicate that there has been a detection change in the way that Windows Server Update Services (WSUS) offers the update for Microsoft SQL Server 2000 Desktop Engine (WMSDE). This is a detection change only. There were no changes to the binaries.

Why was this bulletin revised on July 11, 2008? 
This bulletin was revised to communicate that the Known issues with this security update section in the associated Microsoft Knowledge Base Article 948110 has been updated to describe a detection issue with SKU upgrades for SQL Server 2000 Desktop Engine (WMSDE).

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.

SQL Server Version Range
7.00.1063-7.00.1151 8.00.2039-8.00.2049 8.00.2148-8.00.2272 9.00.3042-9.00.3067 9.00.3150-9.00.3230
SQL Server
SQL Server 7.0 and MSDE 1.0
(KB948113)
SQL Server 2000 GDR and MSDE 2000
(KB948110)
SQL Server 2000 QFE and MSDE 2000
(KB948111)
SQL Server 2005 GDR
(KB948109)
SQL Server 2005 QFE
(KB948108)

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

Why is the QFE Software Update KB948108 not offered to my SQL Server 2005 Service Pack 2 system? 
As detailed in Microsoft Knowledge Base Article 935897, hotfixes for SQL Server 2005 are cumulative. Typically, hotfixes have a shorter testing window than General Distribution Releases (GDR). Customers who have installed either the April Cumulative update package 7 for SQL Server 2005 Service Pack 2 or the June Cumulative update package 8 for SQL Server 2005 Service Pack 2 will not be offered QFE Software Update KB948108, because the security updates available via QFE Software Update KB948108 were already included in both the April and the June cumulative updates. This update still applies for all customers who have not applied either the April or the June cumulative update for SQL Server 2005 Service Pack 2.

The reference tables for SQL Server 2000 and MSDE 2000 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 and MSDE 2000, 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 2000, MSDE 2000, and SQL Server 2005? 
No. Only those instances of SQL Server 2000, MSDE 2000, and SQL Server 2005 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.

Does the update for SQL Server 7.0 Service Pack 4 and Microsoft Data Engine (MSDE) 1.0 Service Pack 4 require manual installation? 
Yes. You will need to manually install the update following the readme instructions in the self-extracting executable file that is provided with the update. For more information on manually installing SQL Server 7.0 Service Pack 4 and Microsoft Data Engine (MSDE) 1.0 Service Pack 4, see Microsoft Knowledge Base Article 953743. For additional installation instructions, see the Security Update Information subsection for SQL Server 7.0 and Microsoft Data Engine (MSDE) in the Update Information section.

I am using an older version 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 versions or editions are affected. Other versions or editions are past their support life cycle. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.

It should be a priority for customers who have older versions or editions of the software to migrate to supported versions or editions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit Microsoft Support Lifecycle. For more information about the extended security update support period for these software versions or editions, visit Microsoft Product Support Services.

Customers who require custom support for older 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 Microsoft Worldwide Information, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ.

Vulnerability Information

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected SoftwareMemory Page Reuse Vulnerability – CVE-2008-0085Convert Buffer Overrun Vulnerability – CVE-2008-0086SQL Server Memory Corruption Vulnerability – CVE-2008-0107SQL Server Buffer Overrun Vulnerability – CVE-2008-0106Aggregate Severity Rating
SQL Server
SQL Server 7.0 Service Pack 4 Important
Information Disclosure
Not Applicable Important
Elevation of Privilege
Not Applicable Important
SQL Server 2000 Service Pack 4 Important
Information Disclosure
Important
Elevation of Privilege
Important
Elevation of Privilege
Not Applicable Important
SQL Server 2000 Itanium-based Edition Service Pack 4 Important
Information Disclosure
Important
Elevation of Privilege
Important
Elevation of Privilege
Not Applicable Important
SQL Server 2005 Service Pack 1 and SQL Server 2005 Service Pack 2 Important
Information Disclosure
Not Applicable Important
Elevation of Privilege
Important
Elevation of Privilege
Important
SQL Server 2005 x64 Edition Service Pack 1 and SQL Server 2005 x64 Edition Service Pack 2 Important
Information Disclosure
Not Applicable Important
Elevation of Privilege
Important
Elevation of Privilege
Important
SQL Server 2005 with SP1 for Itanium-based Systems and SQL Server 2005 with SP2 for Itanium-based Systems Important
Information Disclosure
Not Applicable Important
Elevation of Privilege
Important
Elevation of Privilege
Important
Microsoft Data Engine (MSDE) 1.0 Service Pack 4 Important
Information Disclosure
Not Applicable Important
Elevation of Privilege
Not Applicable Important
Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) Service Pack 4 Important
Information Disclosure
Important
Elevation of Privilege
Important
Elevation of Privilege
Not Applicable Important
Microsoft SQL Server 2005 Express Edition Service Pack 1 and Microsoft SQL Server 2005 Express Edition Service Pack 2 Important
Information Disclosure
Not Applicable Important
Elevation of Privilege
Important
Elevation of Privilege
Important
Microsoft SQL Server 2005 Express Edition with Advanced Services Service Pack 1 and Microsoft SQL Server 2005 Express Edition with Advanced Services Service Pack 2 Important
Information Disclosure
Not Applicable Important
Elevation of Privilege
Important
Elevation of Privilege
Important
Windows Components
Microsoft SQL Server 2000 Desktop Engine (WMSDE) Important
Information Disclosure
Important
Elevation of Privilege
Important
Elevation of Privilege
Not Applicable Important
Windows Internal Database (WYukon) Service Pack 2 Important
Information Disclosure
Not Applicable Important
Elevation of Privilege
Not Applicable Important
Windows Internal Database (WYukon) x64 Edition Service Pack 2 Important
Information Disclosure
Not Applicable Important
Elevation of Privilege
Not Applicable Important

An information disclosure vulnerability exists in the way that SQL Server manages memory page reuse. An attacker with database operator access who successfully exploited this vulnerability could access customer data.

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

Mitigating Factors for Memory Page Reuse Vulnerability Information Disclosure - CVE-2008-0085

Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:

  • This vulnerability requires that an attacker have database operator access to the database, log, database backup files, or log backup files.

Workarounds for Memory Page Reuse Vulnerability Information Disclosure - CVE-2008-0085

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 Common Criteria Compliance on SQL 2005 Service Pack 2

    To enable Common Criteria Compliance, execute the following script while connected to the SQL Server as an administrator. After running the script, restart SQL Server.

    sp_configure 'show advanced options', 1;
    GO
    RECONFIGURE;
    GO
    sp_configure 'common criteria compliance enabled', 1;
    GO
    RECONFIGURE
    GO

    Impact of workaround. Enabling the Common Criteria Compliance option results in a slight performance degradation.

    How to undo the workaround. To disable Common Criteria Compliance, execute the following script while connected to the SQL Server as an administrator. After running the script, restart SQL Server.

    sp_configure 'show advanced options', 1;
    GO
    RECONFIGURE;
    GO
    sp_configure 'common criteria compliance enabled', 0;
    GO
    RECONFIGURE
    GO

FAQ for Memory Page Reuse Vulnerability Information Disclosure - CVE-2008-0085

What is the scope of the vulnerability? 
An information disclosure vulnerability exists in the way that SQL Server manages memory page reuse. An attacker with database operator access who successfully exploited this vulnerability could access customer data that the attacker would otherwise be prohibited from viewing.

What causes the vulnerability? 
The vulnerability exists in the way that SQL Server manages memory page reuse. When reallocating memory, SQL Server fails to initialize memory pages.

What might an attacker use the vulnerability to do? 
An attacker could read the contents of memory pages that contained data from another user’s session.

How could an attacker exploit the vulnerability? 
An attacker with database operator access could assemble the uninitialized memory pages from another user’s session by directing a backup to a location that the attacker controls.

What systems are primarily at risk from the vulnerability? 
Systems where SQL Server is used by untrusted parties are primarily at risk.

What does the update do? 
The update removes the vulnerability by modifying the way that SQL Server manages page reuse.

How do I clean residual data from my databases? 
The following new system stored procedure is provided to physically clean residual data from the free space area of database pages in environments where the physical security of the data or backup files is at risk:

sp_clean_db_free_space

This stored procedure removes residual information left on database pages as a result of data modification routines in SQL Server. This procedure will clean all pages in all files of the database.

sp_clean_db_free_space
@dbname = 'database_name',
[ @cleaning_delay = 'delay_in_seconds' ]

Arguments

@dbname = 'database_name',

  • The name of the database to clean. dbname is nvarchar(384) and cannot be NULL.

[ @cleaning_delay = 'delay_in_seconds' ]

  • To reduce the impact on the IO system, a delay can be specified between the cleaning of pages. cleaning_delay is int with a default of 0.

The following example cleans all residual information from the AdventureWorks database.

USE Master
GO
EXEC sp_clean_db_free_space
@dbname = 'AdventureWorks';

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued. This security bulletin addresses the privately disclosed vulnerability as well as additional issues discovered through internal investigations.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? 
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.

A vulnerability exists in the convert function in SQL Server that could allow an authenticated attacker to gain elevation of privilege. An attacker who successfully exploited this vulnerability could run code and take complete control of the system.

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

Mitigating Factors for Convert Buffer Overrun - CVE-2008-0086

Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state that could reduce the severity of exploitation of vulnerability. The following mitigating factors may be helpful in your situation:

  • An attacker must have valid Windows logon credentials with user permissions to SQL in order to exploit this vulnerability.

Workarounds for Convert Buffer Overrun - CVE-2008-0086

Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:

  • Microsoft has not identified any workarounds for this vulnerability.

FAQ for Convert Buffer Overrun - CVE-2008-0086

What is the scope of the vulnerability? 
An elevation of privilege vulnerability exists in the way that SQL Server converts SQL expressions from one data type to another. This vulnerability could allow an attacker to run code and take complete control of the system. An authenticated attacker could then install programs; view, change, or delete data; or create new accounts with full administrative rights.

What causes the vulnerability? 
The convert function in SQL Server insufficiently checks input strings. As a result, a buffer overrun could result, allowing an authenticated attacker to execute code of the attacker’s choice.

What might an attacker use the vulnerability to do? 
An authenticated attacker who successfully exploited this vulnerability could gain elevation of privilege on an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full administrative rights.

How could an attacker exploit the vulnerability? 
An authenticated attacker could create a query that calls the convert function with a specially crafted expression, causing the function to overflow, allowing code execution.

What systems are primarily at risk from the vulnerability? 
Systems where SQL Server 2000 Service Pack 4 and Microsoft SQL Server 2000 Desktop Engine (WMSDE) is used are primarily at risk.

What does the update do? 
The update removes the vulnerability by allocating more memory for the convert function.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued. This security bulletin addresses the privately disclosed vulnerability as well as additional issues discovered through internal investigations.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? 
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.

A vulnerability exists in SQL Server that could allow an authenticated attacker to gain elevation of privilege. An attacker who successfully exploited this vulnerability could run code and take complete control of the system.

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

Mitigating Factors for SQL Server Memory Corruption Vulnerability - CVE-2008-0107

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:

  • An attacker must have valid Windows logon credentials with user permissions to SQL in order to exploit this vulnerability.

Workarounds for SQL Server Memory Corruption Vulnerability - CVE-2008-0107

Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:

  • Microsoft has not identified any workarounds for this vulnerability.

FAQ for SQL Server Memory Corruption Vulnerability - CVE-2008-0107

What is the scope of the vulnerability? 
An elevation of privilege vulnerability exists in the way that SQL Server validates data structures in on-disk files. This vulnerability could allow an authenticated attacker to run code and to take complete control of the system. An attacker could then install programs; view, change, or delete data; or create new accounts with full administrative rights.

What causes the vulnerability? 
SQL Server fails to sufficiently validate data structures in on-disk files. As a result, a buffer overrun could result and allow an authenticated attacker to execute code of the attacker’s choice.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could gain elevation of privilege on an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full administrative rights.

How could an attacker exploit the vulnerability? 
An authenticated attacker could force SQL Server to load a specially crafted file which could cause a buffer overrun, thus corrupting memory in such a way as to allow code execution.

What systems are primarily at risk from the vulnerability? 
All systems where SQL Server is used are at risk from exploitation of this vulnerability.

What does the update do? 
The update removes the vulnerability by validating on-disk files before loading.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued. This security bulletin addresses the privately disclosed vulnerability as well as additional issues discovered through internal investigations.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? 
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.

A vulnerability exists in SQL Server that could allow an authenticated attacker to gain elevation of privilege. An attacker who successfully exploited this vulnerability could run code and take complete control of the system.

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

Mitigating Factors for SQL Server Buffer Overrun Vulnerability - CVE-2008-0106

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:

  • An attacker must have valid Windows logon credentials with user permissions to SQL in order to exploit this vulnerability.
  • By default, SQL Server 2005 does not run with system privileges.
  • By default, SQL Server 2005 prompts the administrator to choose a domain user account during the install. If the installer configured SQL Server 2005 to run as a non-privileged domain account, this domain account could be less impacted by attempts to exploit this vulnerability.

Workarounds for SQL Server Buffer Overrun Vulnerability - CVE-2008-0106

Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:

  • Microsoft has not identified any workarounds for this vulnerability.

FAQ for SQL Server Buffer Overrun Vulnerability - CVE-2008-0106

What is the scope of the vulnerability? 
An elevation of privilege vulnerability results from the way that SQL Server manages memory in processing the insert statement. This vulnerability could allow an authenticated attacker to run code and take complete control of the system. An attacker could then install programs; view, change, or delete data; or create new accounts with full administrative rights.

What causes the vulnerability? 
SQL Server insufficiently checks insert statements before processing them. As a result, a buffer overrun could result and allow an authenticated attacker to execute code of the attacker’s choice.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could gain elevation of privilege on an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full administrative rights.

How could an attacker exploit the vulnerability? 
An authenticated attacker could create insert statements that cause a buffer overrun, thus corrupting memory in such a way as to allow code execution.

What systems are primarily at risk from the vulnerability? 
Systems where SQL Server 2005 is used are primarily at risk.

What does the update do? 
The update removes the vulnerability by validating insert statements.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued. This security bulletin addresses the privately disclosed vulnerability as well as additional issues discovered through internal investigations.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? 
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.

Update Information

Manage the software and security updates you need to deploy to the servers, desktop, and mobile computers in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.

Security updates are available from Microsoft Update, Windows Update, and Office Update. Security updates are also available at the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update."

Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, “MS07-036”), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ.

Detection and Deployment Guidance

Microsoft has provided detection and deployment guidance for this month’s security updates. This guidance will also help IT professionals understand how they can use various tools to help deploy the security update, such as Windows Update, Microsoft Update, Office Update, the Microsoft Baseline Security Analyzer (MBSA), the Office Detection Tool, Microsoft Systems Management Server (SMS), the Extended Security Update Inventory Tool, and the Enterprise Update Scan Tool (EST). For more information, see Microsoft Knowledge Base Article 910723.

Microsoft Baseline Security Analyzer

Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA, visit Microsoft Baseline Security Analyzer.

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

SoftwareMBSA 2.1
SQL Server 7.0 Service Pack 4No
SQL Server 2000 Service Pack 4Yes
SQL Server 2000 Itanium-based Edition Service Pack 4Yes
SQL Server 2005 Service Pack 2Yes
SQL Server 2005 x64-based Edition Service Pack 2Yes
SQL Server 2005 with SP2 for Itanium-based SystemsYes
Microsoft Data Engine (MSDE) 1.0 Service Pack 4No
Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) Service Pack 4Yes
Microsoft SQL Server 2005 Express Edition Service Pack 2Yes
Microsoft SQL Server 2005 Express Edition with Advanced Services Service Pack 2Yes
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2Yes
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2Yes
Windows Server 2008 and Windows Server 2008 for x64-based SystemsYes

For more information about MBSA 2.1, see MBSA 2.1 Frequently Asked Questions.

Windows Server Update Services

By using Windows Server Update Services (WSUS), administrators can deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003 and later, and SQL Server 2000 and later. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site.

Systems Management Server

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

SoftwareSMS 2.0SMS 2003 with SUSFPSMS 2003 with ITMUSCCM 2007
SQL Server 7.0 Service Pack 4NoNoNoNo
SQL Server 2000 Service Pack 4NoNoYesYes
SQL Server 2000 Itanium-based Edition Service Pack 4NoNoYesYes
SQL Server 2005 Service Pack 2NoNoYesYes
SQL Server 2005 x64-based Edition Service Pack 2NoNoYesYes
SQL Server 2005 with SP2 for Itanium-based SystemsNoNoYesYes
Microsoft Data Engine (MSDE) 1.0 Service Pack 4NoNoNoNo
Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) Service Pack 4NoNoYesYes
Microsoft SQL Server 2005 Express Edition Service Pack 2NoNoYesYes
Microsoft SQL Server 2005 Express Edition with Advanced Services Service Pack 2NoNoYesYes
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2NoNoYesYes
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2NoNoYesYes
Windows Server 2008 and Windows Server 2008 for x64-based SystemsNoNoSee Note for Windows Server 2008 belowYes

For SMS 2.0 and SMS 2003, the SMS SUS Feature Pack (SUSFP), which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. See also Downloads for Systems Management Server 2.0.

For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications. For more information about the Office Inventory Tool and other scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.

System Center Configuration Manager (SCCM) 2007 uses WSUS 3.0 for detection of updates. For more information about SCCM 2007 Software Update Management, visit System Center Configuration Manager 2007.

Note for Windows Server 2008 Microsoft Systems Management Server 2003 with Service Pack 3 includes support for Windows Server 2008 manageability.

For more information about SMS, visit the SMS Web site.

For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.

Update Compatibility Evaluator and Application Compatibility Toolkit

Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit 5.0.

The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.

Affected Software

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

SQL Server 7.0 and Microsoft Data Engine (MSDE)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs No future service packs are planned for SQL Server 7.0
Deployment
Manual installationUpdate files for SQL 7.0 are provided in a self-extracting executable file from the Microsoft Download Center link in the Affected Software table. A README file with instructions for manual installation is included in the SQL 7.0 update files.
Update log fileNone
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart requiredYes, you must restart your system after you apply this security update
HotpatchingThis security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341.
Removal Information Update files for SQL 7.0 are provided in a self-extracting executable file from the Microsoft Download Center link in the Affected Software table. Instructions for manually uninstalling the update are provided in an attached README file.
File Information See Microsoft Knowledge Base Article 941203

Deployment Information

Installing the Update

Update files for SQL 7.0 are provided in a self-extracting executable file from the Microsoft Download Center link in the Affected Software table. Instructions for manual installation are provided in an attached README file.

Removing the Update

Update files for SQL 7.0 are provided in a self-extracting executable file from the Microsoft Download Center link in the Affected Software table. Instructions for manually uninstalling the update are provided in an attached README file.

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 2000 and Microsoft SQL Server Desktop Engine (MSDE)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs No future service packs are planned for SQL Server 2000
Deployment
Installing without user interventionFor GDR update of SQL Server 2000 installed on all supported 32-bit and x64-based systems:
SQL2000-KB948110-v8.00.2050-x86x64-ENU /quiet /allinstances
For GDR update of all supported Itanium-based editions of SQL Server 2000:
SQL2000-KB948110-v8.00.2050-ia64-ENU /quiet /allinstances
For QFE update of SQL Server 2000 installed on all supported 32-bit and x64-based systems:
SQL2000-KB948111-v8.00.2273-x86x64-ENU /quiet /allinstances
For QFE update of all supported Itanium-based editions of SQL Server 2000:
SQL2000-KB948111-v8.00.2273-ia64-ENU /quiet /allinstances
Installing without restartingFor GDR update of SQL Server 2000 installed on all supported 32-bit and x64-based systems:
SQL2000-KB948110-v8.00.2050-x86x64-ENU /norestart /allinstances
For GDR update of all supported Itanium-based editions of SQL Server 2000:
SQL2000-KB948110-v8.00.2050-ia64-ENU /norestart /allinstances
For QFE update of SQL Server 2000 installed on all supported 32-bit and x64-based systems:
SQL2000-KB948111-v8.00.2273-x86x64-ENU /norestart /allinstances
For QFE update of all supported Itanium-based editions of SQL Server 2000:
SQL2000-KB948111-v8.00.2273-ia64-ENU /norestart /allinstances
Installing a single instanceFor GDR update of SQL Server 2000 installed on all supported 32-bit and x64-based systems:
SQL2000-KB948110-v8.00.2050-x86x64-ENU /quiet /InstanceName={instance}
For GDR update of all supported Itanium-based editions of SQL Server 2000:
SQL2000-KB948110-v8.00.2050-ia64-ENU /quiet /InstanceName={instance}
For QFE update of SQL Server 2000 installed on all supported 32-bit and x64-based systems:
SQL2000-KB948111-v8.00.2273-x86x64-ENU /quiet /InstanceName={instance}
For QFE update of all supported Itanium-based editions of SQL Server 2000:
SQL2000-KB948111-v8.00.2273-ia64-ENU /quiet /InstanceName={instance}
For GDR update of SQL Server 2000 installed on all supported 32-bit and x64-based systems:
SQL2000-KB948110-v8.00.2050-x86x64-ENU /norestart /InstanceName={instance}
For GDR update of all supported Itanium-based editions of SQL Server 2000:
SQL2000-KB948110-v8.00.2050-ia64-ENU /norestart /InstanceName={instance}
For QFE update of SQL Server 2000 installed on all supported 32-bit and x64-based systems:
SQL2000-KB948111-v8.00.2273-x86x64-ENU /norestart /InstanceName={instance}
For QFE update of all supported Itanium-based editions of SQL Server 2000:
SQL2000-KB948111-v8.00.2273-ia64-ENU /norestart /InstanceName={instance}
Update log fileSQL2000-KB948110-V8.00.2050-x86-<language>.log or SQL2000-KB948111-V8.00.2273-x86-<language>.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart requiredA 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.
HotpatchingThis security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341.
Removal Information For all supported editions of SQL Server 2000:
Use Add or Remove Programs tool in Control Panel
File Information See Microsoft Knowledge Base Article 941203

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
/help Displays the command-line options
Setup Modes
/passive Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart Does not restart when installation has completed
/forcerestart Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x] Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart Display a dialog box prompting the local user to allow a restart
Special Options
/overwriteoem Overwrites OEM files without prompting
/nobackup Does not back up files needed for uninstall
/forceappsclose Forces other programs to close when the computer shuts down
/log:path Allows the redirection of installation log files
/integrate:path Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
/allinstances Applies 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

This security update supports the following setup switches.

Supported Spuninst.exe Switches
SwitchDescription
/help Displays the command-line options
Setup Modes
/passive Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart Does not restart when installation has completed
/forcerestart Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x] Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart Display a dialog box prompting the local user to allow a restart
Special Options
/forceappsclose Forces other programs to close when the computer shuts down
/log:path Allows the redirection of installation log files
/allinstances Applies update to all instances
/InstanceName={instance} Applies update to specified instance

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 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 Packs SQL Server 2005 Service Pack 3
Deployment
Installing without user interventionFor GDR update of all supported 32-bit editions of SQL Server 2005:
SQLServer2005-KB948109-x86-ENU /quiet /allinstances
For GDR update of all supported x64-based editions of SQL Server 2005:
SQLServer2005-KB948109-x64-ENU /quiet /allinstances
For GDR update of all supported Itanium-based editions of SQL Server 2005:
SQLServer2005-KB948109-ia64-ENU /quiet /allinstances
For QFE update of all supported 32-bit editions of SQL Server 2005:
SQLServer2005-KB948108-x86-ENU /quiet /allinstances
For QFE update of all supported x64-based editions of SQL Server 2005:
SQLServer2005-KB948108-x64-ENU /quiet /allinstances
For QFE update of all supported Itanium-based editions of SQL Server 2005:
SQLServer2005-KB948108-ia64-ENU /quiet /allinstances
Installing a single instanceFor GDR update of all supported 32-bit editions of SQL Server 2005:
SQLServer2005-KB948109-x86-ENU /quiet /InstanceName={instance}
For GDR update of all supported x64-based editions of SQL Server 2005:
SQLServer2005-KB948109-x64-ENU /quiet /InstanceName={instance}
For GDR update of all supported Itanium-based editions of SQL Server 2005:
SQLServer2005-KB948109-ia64-ENU /quiet /InstanceName={instance}
For QFE update of all supported 32-bit editions of SQL Server 2005:
SQLServer2005-KB948108-x86-ENU /quiet /InstanceName={instance}
For QFE update of all supported x64-based editions of SQL Server 2005:
SQLServer2005-KB948108-x64-ENU /quiet /InstanceName={instance}
For QFE update of all supported Itanium-based editions of SQL Server 2005:
SQLServer2005-KB948108-ia64-ENU /quiet /InstanceName={instance}
Update log file%programfiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Summary.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart requiredIf 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 Information For all supported editions of SQL Server 2005:
Use Add or Remove Programs tool in Control Panel
File Information See Microsoft Knowledge Base Article 941203

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
/quiet Runs Setup in quiet mode
/reportonly Displays the features that this package can update
/allinstances Upgrades all SQL Server instances and all shared components
/instancename Upgrades a specific SQL Server instance and all shared components
/sapwd Password for the SQL Server sa account to run scripts
/user User account for connecting to a remote cluster node
/password Password for user account for connecting to a remote cluster node
/rsupgradedatabaseaccount User account for upgrading Reporting Services
/rsupgradepassword Password for user account for upgrading Reporting Services
/rsupgradedatabase Prevents the Reporting Services database from being upgraded when the parameter equals 0
/allinstances Applies 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_KB948108_ENU\hotfix.exe /quiet /uninstall /instancename=foo

Example of how to remove QFE from all instances:

%windir%\SQL9_KB948108_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 SQL Server 2000 Desktop Engine (WMSDE) (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs No future service packs are planned for SQL Server 2000 Desktop Engine (WMSDE)
Deployment
Installing without user interventionFor all supported 32-bit editions of SQL Server 2000 Desktop Engine (WMSDE):
SQLWMSDE-KB948110-x86-ENU /quiet /upgradesp sqlrun {BLANKSAPWD=1 or SAPWD=} INSTANCENAME={instancename} /l*v %windir%<yyyyy>.log

Where:
instancename is the product instance name used during install, i.e., either “UDDI,” “SharePoint,” “WSUS,” “MS_ADMT,” or “MicrosoftADS”

for example:
SQLWMSDE-KB948110-x86-ENU.exe /upgradesp sqlrun 1 INSTANCENAME=UDDI /l*v %windir%WMSDE.log
Installing without restartingFor all supported 32-bit editions of SQL Server 2000 Desktop Engine (WMSDE):
SQLWMSDE-KB948110-x86-ENU /norestart /upgradesp sqlrun {BLANKSAPWD=1 or SAPWD=} INSTANCENAME={instancename} /l*v %windir%<yyyyy>.log /norestart

Where:
instancename is the product instance name used during install. i.e., either “UDDI,” “SharePoint,” “WSUS,” “MS_ADMT,” or “MicrosoftADS”

for example:
SQLWMSDE-KB948110-x86-ENU.exe /upgradesp sqlrun 1 INSTANCENAME=UDDI /l*v %windir%WMSDE.log
Update log fileKB948110.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart requiredIf 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 Information For all supported 32-bit editions of SQL Server 2000 Desktop Engine (WMSDE):
Use Add or Remove Programs tool in Control Panel.

Note Removing this security update for WMSDE will completely remove the WMSDE instance from the system.

File Information See Microsoft Knowledge Base Article 941203

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
/help Displays the command-line options
Restart Options
/norestart Does not restart when installation has completed
/forcerestart Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x] Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart Display a dialog box prompting the local user to allow a restart
Special Options
/overwriteoem Overwrites OEM files without prompting
/nobackup Does not back up files needed for uninstall
/forceappsclose Forces other programs to close when the computer shuts down
/log:path Allows the redirection of installation log files
/integrate:path Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
/extract[:path] Extracts files without starting the Setup program
/ER Enables extended error reporting
/verbose Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.
/allinstances Applies 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

Note Removing this security update for WMSDE will completely remove the WMSDE instance from the system.

Uninstall commands for WMSDE:

MS_ADMT

msiexec /x {EEE5C104-B67A-486D-947E-A209F2058E93} /qn reboot=reallysupress /l*v %windir%\results\AdmtUn.log

MicrosoftADS

msiexec /x {B3E6E30F-7680-4DF9-A152-B5285098A5AD} /qn reboot=reallysupress /l*v %windir%\results\AdsUn.log

SharePoint

msiexec /x {65657C59-23A8-4974-B8E0-BA04EBD04E4F} /qn reboot=reallysupress /l*v %windir%\results\SharepointUn.log

UDDI

msiexec /x {B42339CD-9F22-4A6A-A023-D12990E0B918} /qn reboot=reallysupress /l*v %windir%\results\UddiUn.log

WSUS

msiexec /x {83BC1BC2-FCC4-4CED-8A3C-EB7CDFB3CF6A} /qn reboot=reallysupress /l*v %windir%\results\WsusUn.log

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.

Windows Internal Database (WYukon) (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs Windows Internal Database (WYukon) Service Pack 3
Deployment
Installing without user interventionFor all supported 32-bit editions of Windows Internal Database (WYukon):
WYukon2005Setup-KB948109-x86-ENU /quiet
For all supported 64-bit editions of Windows Internal Database (WYukon):
WYukon2005Setup-KB948109-x64-ENU /quiet
Installing without restartingFor all supported 32-bit editions of Windows Internal Database (WYukon):
WYukon2005Setup-KB948109-x86-ENU /norestart
For all supported 32-bit editions of Windows Internal Database (WYukon):
WYukon2005Setup-KB948109-x64-ENU /norestart
Update log fileSSEE_10.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart requiredYes, you must restart your system after you apply this security update
HotpatchingThis security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341.
Removal Information For all supported editions of Windows Internal Database (WYukon):
Use Add or Remove Programs tool in Control Panel.

Note Removing this security update for WYukon will completely remove the WYukon instance from the system.

File Information See Microsoft Knowledge Base Article 941203

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
/help Displays the command-line options
Restart Options
/norestart Does not restart when installation has completed
/forcerestart Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x] Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart Display a dialog box prompting the local user to allow a restart
Special Options
/overwriteoem Overwrites OEM files without prompting
/nobackup Does not back up files needed for uninstall
/forceappsclose Forces other programs to close when the computer shuts down
/log:path Allows the redirection of installation log files
/integrate:path Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
/extract[:path] Extracts files without starting the Setup program
/ER Enables extended error reporting
/verbose Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.

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

Acknowledgments

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

  • An anonymous finder for reporting the Memory Page Reuse Vulnerability (CVE-2008-0085).
  • An anonymous finder for reporting the Convert Buffer Overrun Vulnerability (CVE-2008-0086).
  • Brett Moore of Insomnia Security working with the iDefense VCP for reporting the SQL Server Memory Corruption Vulnerability (CVE-2008-0107).
  • An anonymous finder for reporting the SQL Server Buffer Overrun Vulnerability (CVE-2008-0106).

Support

  • Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.
  • International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.

Disclaimer

The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.

Revisions

  • V1.0 (July 8, 2008): Bulletin published.
  • V1.1 (July 9, 2008): Removed erroneous references to SQL Server 2005 Service Pack 1 in the MBSA and SMS Detection and Deployment tables. Also clarified permissions requirements for vulnerability mitigating factors.
  • V1.2 (July 11, 2008): Added entry to the Frequently Asked Questions (FAQ) Related to This Security Update to communicate that the Known issues with this security update section in the associated Microsoft Knowledge Base Article 948110 has been updated.
  • V1.3 (July 16, 2008): Updated the applicable software under the “Windows Server Update Services” heading in the section, Detection and Deployment Tools and Guidance.
  • V1.4 (July 18, 2008): Corrected the list of valid product instance names in the Microsoft SQL Server 2000 Desktop Engine (WMSDE) subsection under the Security Update Information section. Also added entry to the Frequently Asked Questions (FAQ) Related to This Security Update to communicate a detection change in the way that Windows Server Update Services (WSUS) offers the update for Microsoft SQL Server 2000 Desktop Engine (WMSDE).
  • V1.5 (July 23, 2008): Added removal information notes for Microsoft SQL Server 2000 Desktop Engine (WMSDE) and Windows Internal Database (WYukon) to clarify that removing this security update for WMSDE or WYukon will also completely remove the instance of WMSDE or WYukon from the system.
  • V1.6 (August 12, 2008): Added entry to the Frequently Asked Questions (FAQ) Related to This Security Update to communicate a change in the installation code for the security update for SQL Server 2005 Service Pack 2. This is an installation code change only. There were no changes to the security update binaries.
  • V1.7 (January 21, 2009): Listed Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) Service Pack 3a, a component of Application Center 2000 Service Pack 2, as non-affected software.
  • V1.8 (February 11, 2009): Removed erroneous reference to Microsoft SQL Server 2000 Desktop Engine (WMSDE) on Microsoft Windows 2000 Service Pack 4 from the Affected Software table for Windows Components. Also changed the log file entry in the Reference table for Windows Internal Database (WYukon) in the Security Update Deployment section.
  • V1.9 (March 18, 2009): Corrected product instance names from "ADMT" and "ADS" to "MS_ADMT" and "MicrosoftADS", respectively. These are instance names referenced in the Security Update Deployment section for the Microsoft SQL Server 2000 Desktop Engine (WMSDE). This is an informational change only that does not affect the files contained in the update. Customers who have successfully updated their systems do not need to reinstall this update.

Built at 2014-04-18T13:49:36Z-07:00

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2015 Microsoft