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

Microsoft Security Bulletin MS07-009 - Critical

Vulnerability in Microsoft Data Access Components Could Allow Remote Code Execution (927779)

Published: February 13, 2007

Version: 1.0

Summary

Who Should Read this Document: Customers who use Microsoft Windows

Impact of Vulnerability: Remote Code Execution

Maximum Severity Rating: Critical

Recommendation: Customers should apply the update immediately

Security Update Replacement: This bulletin replaces a prior security update. See the frequently asked questions (FAQ) section of this bulletin for the complete list.

Caveats: None

Tested Software and Security Update Download Locations:

Affected Software:

  • Microsoft Data Access Components 2.5 Service Pack 3 on Microsoft Windows 2000 Service Pack 4 – Download the update
  • Microsoft Data Access Components 2.8 Service Pack 1 on Microsoft Windows XP Service Pack 2 — Download the update
  • Microsoft Data Access Components 2.8 on Microsoft Windows Server 2003 — Download the update
  • Microsoft Data Access Components 2.8 on Microsoft Windows Server 2003 for Itanium-based Systems — Download the update

Non-Affected Software:

  • Microsoft Data Access Components 2.8 Service Pack 2 on Microsoft Windows XP Professional x64 Edition
  • Microsoft Data Access Components 2.8 Service Pack 2 on Microsoft Windows Server 2003 Service Pack 1
  • Microsoft Data Access Components 2.8 Service Pack 2 on Microsoft Windows Server 2003 with SP1 for Itanium-based Systems
  • Microsoft Data Access Components 2.8 Service Pack 2 on Microsoft Windows Server 2003 x64 Edition
  • Windows Data Access Components 6.0 on Windows Vista

Tested Microsoft Windows Components:

Affected Components:

  • Microsoft Data Access Components 2.7 Service Pack 1 when installed on Microsoft Windows 2000 Service Pack 4 — Download the update
  • Microsoft Data Access Components 2.8 when installed on Microsoft Windows 2000 Service Pack 4 — Download the update
  • Microsoft Data Access Components 2.8 Service Pack 1 when installed on Microsoft Windows 2000 Service Pack 4 — Download the update

Note The “Affected Software” section applies to MDAC that shipped with a Microsoft Windows operating system. The “Affected Components” section applies to MDAC that was downloaded and installed onto a Microsoft Windows operating system.

Note Microsoft strongly recommends that all customers who currently use a version of Windows that does not have Microsoft Data Access Components 2.7 Service Pack 1 or higher upgrade immediately to Microsoft Data Access Components 2.8 Service Pack 1 or another supported version. The only exception to this notice is customers who currently use Windows 2000 Service Pack 4 running Microsoft Data Access Components 2.5 Service Pack 3. See Knowledge Base Article 915387 for more information.

The software in this list has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.

General Information

Executive Summary:

This update resolves a public vulnerability. The vulnerability is documented in the "Vulnerability Details" section of this bulletin.

If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

We recommend that customers apply the update immediately.

Severity Ratings and Vulnerability Identifiers:

Vulnerability IdentifiersImpact of VulnerabilityMicrosoft Windows 2000 Service Pack 4Microsoft Windows XP Service Pack 2Microsoft Windows Server 2003
Microsoft Windows MDAC ActiveX Vulnerability - CVE-2006-5559Remote Code ExecutionCriticalCriticalModerate

This assessment is based on the types of systems that are affected by the vulnerability, their typical deployment patterns, and the effect that exploiting the vulnerability would have on them.

Note By default, Internet Explorer on Windows Server 2003 runs in a restricted mode that is known as Enhanced Security Configuration. See the FAQ section for this security update for more information about Internet Explorer Enhanced Security Configuration.

Note The severity ratings for non-x86 operating system versions map to the x86 operating systems versions as follows:

  • The Windows Server 2003 for Itanium-based Systems severity rating is the same as the Windows Server 2003 severity rating.

Can I detect what version of MDAC is installed on my system?
Yes, there is a tool available that you can use to determine the version of MDAC that you have installed on your system. For more information about how to install and use this tool, see Microsoft Knowledge Base Article 301202. For information about the different MDAC versions that are available and the products that install them, see Microsoft Knowledge Base Article 231943.

I am currently using Microsoft Data Access Components 2.6 or 2.6 Service Pack 1. Neither is mentioned in this update. What do I do?
Microsoft Data Access Components 2.6 and Microsoft Data Access Components 2.6 Service Pack 1 have reached the end of their support life cycles. It should be a priority for customers who have these versions to migrate to the supported version. The supported version is Microsoft Data Access Components 2.8 Service Pack 1.

What updates does this release replace?
This security update replaces a prior security update. The security bulletin ID and affected operating systems are listed in the following table.

Bulletin IDMicrosoft Data Access Components 2.5 Service Pack 3 on Microsoft Windows 2000 Service Pack 4Microsoft Data Access Components 2.7 Service Pack 1 when installed on Microsoft Windows 2000 Service Pack 4Microsoft Data Access Components 2.8 when installed on Microsoft Windows 2000 Service Pack 4Microsoft Data Access Components 2.8 Service Pack 1 when installed on Microsoft Windows 2000 Service Pack 4Microsoft Data Access Components 2.8 Service Pack 1 on Microsoft Windows XP Service Pack 2Microsoft Data Access Components 2.8 on Microsoft Windows Server 2003Microsoft Data Access Components 2.8 on Microsoft Windows Server 2003 for Itanium-based Systems
MS06-014 ReplacedReplacedReplacedReplacedNot ReplacedNot ReplacedNot Replaced

Extended security update support for Microsoft Windows XP Home Edition Service Pack 1 or Service Pack 1a, Windows XP Media Center Edition 2002 Service Pack 1, Windows XP Media Center Edition 2004 Service Pack 1, Windows XP Professional Service Pack 1 or Service Pack 1a, and Windows XP Tablet PC Edition Service Pack 1 ended on October 10, 2006. I am still using one of these operating systems; what should I do?
Windows XP (all versions) Service Pack 1 has reached the end of its support life cycle. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.

Extended security update support for Microsoft Windows 98, Windows 98 Second Edition, or Windows Millennium Edition ended on July 11, 2006. I am still using one of these operating systems; what should I do? 
Windows 98, Windows 98 Second Edition, and Windows Millennium Edition have reached the end of their support life cycles. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.

Extended security update support for Microsoft Windows NT Workstation 4.0 Service Pack 6a and Windows 2000 Service Pack 2 ended on June 30, 2004. Extended security update support for Microsoft Windows NT Server 4.0 Service Pack 6a ended on December 31, 2004. Extended security update support for Microsoft Windows 2000 Service Pack 3 ended on June 30, 2005. I am still using one of these operating systems; what should I do?
Windows NT Workstation 4.0 Service Pack 6a, Windows NT Server 4.0 Service Pack 6a, Windows 2000 Service Pack 2, and Windows 2000 Service Pack 3 have reached the end of their support life cycles. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.

Customers who require custom support for these products must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country, 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.

For more information, visit the Windows Operating System FAQ.

Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine whether this update is required?
The following table provides the MBSA detection summary for this security update.

ProductMBSA 1.2.1ESTMBSA 2.0
Microsoft Windows 2000 Service Pack 4NoYesYes
Microsoft Windows XP Service Pack 2YesNot ApplicableYes
Microsoft Windows Server 2003YesNot ApplicableYes
Microsoft Windows Server 2003 for Itanium-based SystemsNoNoYes

For more information about MBSA, visit the MBSA Web site. For more information about the programs that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660.

For more detailed information, see Microsoft Knowledge Base Article 910723.

What is the Enterprise Update Scan Tool (EST)?
As part of an ongoing commitment to provide detection tools for bulletin-class security updates, Microsoft delivers a stand-alone detection tool whenever the Microsoft Baseline Security Analyzer (MBSA) and the Office Detection Tool (ODT) cannot detect whether the update is required for an MSRC release cycle. This stand-alone tool is called the Enterprise Update Scan Tool (EST) and is designed for enterprise administrators. When a version of the Enterprise Update Scan Tool is created for a specific bulletin, customers can run the tool from a command-line interface (CLI) and view the results of the XML output file. To help customers better utilize the tool, detailed documentation will be provided with the tool. There is also a version of the tool that offers an integrated experience for SMS administrators.

Can I use a version of the Enterprise Update Scan Tool (EST) to determine whether this update is required?
Yes. Microsoft has created a version of EST that will determine if you have to apply this update. For download links and more information about the version of EST that is being released this month, see Microsoft Knowledge Base Article 894193. SMS customers should review the following FAQ, “Can I use Systems Management Server (SMS) to determine whether this update is required?" for more information about SMS and EST.

Can I use Systems Management Server (SMS) to determine whether this update is required?
The following table provides the SMS detection summary for this security update.

ProductSMS 2.0SMS 2003
Microsoft Windows 2000 Service Pack 4Yes (with EST)Yes
Microsoft Windows XP Service Pack 2YesYes
Microsoft Windows Server 2003YesYes
Microsoft Windows Server 2003 for Itanium-based SystemsNoYes

SMS 2.0 and SMS 2003 Software Update Services (SUS) Feature Pack can use MBSA 1.2.1 for detection and therefore have the same limitation that is listed earlier in this bulletin related to programs that MBSA 1.2.1 does not detect.

For SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about SUIT, visit the following Microsoft Web site. For more information about the limitations of SUIT, see Microsoft Knowledge Base Article 306460. The SMS SUS Feature Pack also includes the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

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, visit the following Microsoft Web site. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

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

For more detailed information, see Microsoft Knowledge Base Article 910723.

Microsoft Windows MDAC ActiveX Vulnerability - CVE-2006-5559:

A remote code execution vulnerability exists in the ADODB.Connection ActiveX control that is provided as part of the ActiveX Data Objects (ADO) and that is distributed in MDAC. An attacker who successfully exploited this vulnerability could take complete control of an affected system.

Mitigating Factors for Microsoft Windows MDAC ActiveX Vulnerability - CVE-2006-5559:

  • In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to exploit this vulnerability. An attacker would have no way to force users to visit the page. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or instant messenger message that takes users to the attacker's Web site.
  • An attacker who successfully exploited this vulnerability could gain the same user rights as the logged on user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
  • By default, all supported versions of Microsoft Outlook and Microsoft Outlook Express open HTML e-mail messages in the Restricted sites zone. The Restricted sites zone helps reduce attacks that could try to exploit this vulnerability by preventing Active Scripting and ActiveX controls from being used when reading HTML e-mail. However, if a user clicks on a link within an e-mail they could still be vulnerable to this issue through the Web-based attack scenario.
  • By default, Internet Explorer on Windows Server 2003 runs in a restricted mode that is known as Enhanced Security Configuration. This mode sets the security level for the Internet zone to High. This is a mitigating factor for Web sites that have not been added to Internet Explorer Trusted sites zone. See the FAQ section of this security update for more information about Internet Explorer Enhanced Security Configuration.

Workarounds for Microsoft Windows MDAC ActiveX Vulnerability - CVE-2006-5559:

Microsoft has tested the following workarounds. Although these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified in the following section.

  • Prevent the ADODB.Connection ActiveX Control from running in Internet Explorer

    Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

    1. Save the following text to a .reg file and then run it on the vulnerable client.

      Windows Registry Editor Version 5.00

      [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{00000514-0000-0010-8000-00AA006D2EA4}]
      Compatibility Flags=dword:00000400
    2. You can apply this .reg file to individual systems by double-clicking it. You can also apply it across domains by using Group Policy. For more information about Group Policy, visit the following Microsoft Web sites:

      Group Policy collection
      What is Group Policy Object Editor?
      Core Group Policy tools and settings

    Impact of Workaround: Disables some MDAC functionality from within Internet Explorer.

    To Rollback:

    Remove the above registry entry from the registry.

  • Unregister the ADO ActiveX controls

    Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

    • At the command prompt run the following:

      regsvr32 -u "%CommonProgramFiles%\System\ado\msado15.dll”

    Impact of Workaround: This will likely break lots of MDAC functionality, more intrusive than the killbit above.

    To Rollback:

    • At the command prompt run the following:

      regsvr32 "%CommonProgramFiles%\System\ado\msado15.dll”
  • Configure Internet Explorer to prompt before running ActiveX Controls or disable ActiveX Controls in the Internet and Local intranet security zone

    You can help protect against this vulnerability by changing your Internet Explorer settings to prompt before running ActiveX controls. To do this, follow these steps:

    1. In Internet Explorer, click Internet Options on the Tools menu.
    2. Click the Security tab.
    3. Click Internet, and then click Custom Level.
    4. Under Settings, in the ActiveX controls and plug-ins section, under Run ActiveX controls and plug-ins, click Prompt or Disable, and then click OK.
    5. Click Local intranet, and then click Custom Level.
    6. Under Settings, in the ActiveX controls and plug-ins section, under Run ActiveX controls and plug-ins, click Prompt or Disable, and then click OK.
    7. Click OK two times to return to Internet Explorer.

    Impact of Workaround: There are side effects to prompting before running ActiveX controls. Many Web sites that are on the Internet or on an intranet use ActiveX to provide additional functionality. For example, an online e-commerce site or banking site may use ActiveX controls to provide menus, ordering forms, or even account statements. Prompting before running ActiveX controls is a global setting that affects all Internet and intranet sites. You will be prompted frequently when you enable this workaround. For each prompt, if you feel you trust the site that you are visiting, click Yes to run ActiveX controls. If you do not want to be prompted for all these sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone”.

    Add sites that you trust to the Internet Explorer Trusted sites zone.

    After you set Internet Explorer to require a prompt before it runs ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect you from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.

    To do this, follow these steps:

    1. In Internet Explorer, click Tools, click Internet Options, and then click the Security tab.
    2. In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites.
    3. If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.
    4. In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.
    5. Repeat these steps for each site that you want to add to the zone.
    6. Click OK two times to accept the changes and return to Internet Explorer.

    Note Add any sites that you trust not to take malicious action on your computer. Two in particular that you may want to add are "*.windowsupdate.microsoft.com" and “*.update.microsoft.com” (without the quotation marks). These are the sites that will host the update, and it requires an ActiveX Control to install the update.

  • Set Internet and Local intranet security zone settings to “High” to prompt before running ActiveX Controls and Active Scripting in these zones

    You can help protect against this vulnerability by changing your settings for the Internet security zone to prompt before running ActiveX controls. You can do this by setting your browser security to High.

    To raise the browsing security level in Microsoft Internet Explorer, follow these steps:

    1. On the Internet Explorer Tools menu, click Internet Options.
    2. In the Internet Options dialog box, click the Security tab, and then click the Internet icon.
    3. Under Security level for this zone, move the slider to High. This sets the security level for all Web sites you visit to High.

    Note If no slider is visible, click Default Level, and then move the slider to High.

    Note Setting the level to High may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly even with the security setting set to High.

    Impact of Workaround: There are side effects to prompting before running ActiveX controls. Many Web sites that are on the Internet or on an intranet use ActiveX to provide additional functionality. For example, an online e-commerce site or banking site may use ActiveX controls to provide menus, ordering forms, or even account statements. Prompting before running ActiveX controls is a global setting that affects all Internet and intranet sites. You will be prompted frequently when you enable this workaround. For each prompt, if you feel you trust the site that you are visiting, click Yes to run ActiveX controls. If you do not want to be prompted for all these sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone”.

    Add sites that you trust to the Internet Explorer Trusted sites zone.

    After you set Internet Explorer to require a prompt before it runs ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect you from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.

    To do this, follow these steps:

    1. In Internet Explorer, click Tools, click Internet Options, and then click the Security tab.
    2. In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites.
    3. If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.
    4. In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.
    5. Repeat these steps for each site that you want to add to the zone.
    6. Click OK two times to accept the changes and return to Internet Explorer.

    Note Add any sites that you trust not to take malicious action on your computer. Two in particular that you may want to add are "*.windowsupdate.microsoft.com" and “*.update.microsoft.com” (without the quotation marks). These are the sites that will host the update, and it requires an ActiveX Control to install the update.

FAQ for Microsoft Windows MDAC ActiveX Vulnerability - CVE-2006-5559:

What is the scope of the vulnerability?
A remote code execution vulnerability exists in the ADODB.Connection ActiveX control that is provided as part of the ActiveX Data Objects (ADO) and that is distributed in MDAC. If a user were logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less affected than users who operate with administrative rights.

What causes the vulnerability?
The ADODB.Connection ActiveX control included in MDAC could, if passed unexpected data, cause Internet Explorer to fail in a way that could allow code execution.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system.

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

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

I am running Internet Explorer on Windows Server 2003. Does this mitigate this vulnerability?
Yes. By default, Internet Explorer on Windows Server 2003 runs in a restricted mode that is known as Enhanced Security Configuration. This mode sets the security level for the Internet zone to High. This is a mitigating factor for Web sites that have not been added to Internet Explorer Trusted sites zone.

What is the Internet Explorer Enhanced Security Configuration?
Internet Explorer Enhanced Security Configuration is a group of preconfigured Internet Explorer settings that reduce the likelihood of a user or of an administrator downloading and running specially crafted Web content on a server. Internet Explorer Enhanced Security Configuration reduces this risk by modifying many security-related settings. This includes the settings on the Security tab and the Advanced tab in the Internet Options dialog box. Some of the important modifications include the following:

Security level for the Internet zone is set to High. This setting disables scripts, ActiveX controls, Microsoft Java Virtual Machine (MSJVM), and file downloads.

Automatic detection of intranet sites is disabled. This setting assigns all intranet Web sites and all Universal Naming Convention (UNC) paths that are not explicitly listed in the Local intranet zone to the Internet zone.

Install On Demand and non-Microsoft browser extensions are disabled. This setting prevents Web pages from automatically installing components and prevents non-Microsoft extensions from running.

Multimedia content is disabled. This setting prevents music, animations, and video clips from running.

For more information regarding Internet Explorer Enhanced Security Configuration, see the guide, Managing Internet Explorer Enhanced Security Configuration, at the following Web site.

What does the update do?
The update removes the vulnerability by modifying the way that the ADODB.Connection ActiveX control performs parameter validation.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. This vulnerability has been publicly disclosed. It has been assigned Common Vulnerability and Exposure number CVE-2006-5559.

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

Affected Software:

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

Microsoft Data Access Components when installed on Windows 2000 (all versions)

Prerequisites
For Windows 2000, this security update requires Service Pack 4 (SP4). For Small Business Server 2000, this security update requires Small Business Server 2000 Service Pack 1a (SP1a) or Small Business Server 2000 running with Windows 2000 Server Service Pack 4 (SP4).

The software that is listed has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.

For more information about how to obtain the latest service pack, see Microsoft Knowledge Base Article 260910.

Inclusion in Future Service Packs:
The update for this issue may be included in a future Update Rollup.

Installation Information

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/help Displays the command-line options
Setup Modes
/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.
/extract[:path] Extracts files without starting the Setup program
/ER Enables extended error reporting
/verbose Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

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

Deployment Information

Note If you are unsure of the version of MDAC you are running, install the Component Checker.

To install the security update without any user intervention, use the following command at a command prompt for Windows 2000 Service Pack 4:

Microsoft Data Access Components 2.5 Service Pack 3:

MDAC253-KB927779-x86-enu /quiet

Microsoft Data Access Components 2.7 Service Pack 1:

MDAC271-KB927779-x86-enu /quiet

Microsoft Data Access Components 2.8:

MDAC28-KB927779-x86-enu /quiet

Microsoft Data Access Components 2.8 Service Pack 1:

MDAC281-KB927779-x86-enu /quiet

Note Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the MDAC253-KB927779-x86-enu.log, MDAC271-KB927779-x86-enu.log, MDAC28-KB927779-x86-enu.log or MDAC281-KB927779-x86-enu.log files for any failure messages when they use this switch.

To install the security update without forcing the system to restart, use the following command at a command prompt for Windows 2000 Service Pack 4:

Microsoft Data Access Components 2.5 Service Pack 3:

MDAC253-KB927779-x86-enu /norestart

Microsoft Data Access Components 2.7 Service Pack 1:

MDAC271-KB927779-x86-enu /norestart

Microsoft Data Access Components 2.8:

MDAC28-KB927779-x86-enu /norestart

Microsoft Data Access Components 2.8 Service Pack 1:

MDAC281-KB927779-x86-enu /norestart

For more information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.

Restart Requirement

This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.

Removal Information

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

System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the following; %Windir%\$SQLUninstallMDAC25SP3-KB927779-x86-enu$\Spuninst, %Windir%\$SQLUninstallMDAC27SP1-KB927779-x86-enu$\Spuninst, %Windir%\$SQLUninstallMDAC28-KB927779-x86-enu$\Spuninst, or %Windir%\$SQLUninstallMDAC28SP1-KB927779-x86-enu$\Spuninst

Supported Spuninst.exe Switches
SwitchDescription
/help Displays the command-line options
Setup Modes
/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

File Information

The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Microsoft Data Access Components 2.5 Service Pack 3:

File NameVersionDateTimeSize
Sprecovr.exe6.2.29.005-Jan-200716:4929,408
Spupdsvc.exe6.2.29.005-Jan-200716:4922,752
Msadce.dll2.53.6307.010-Jan-200719:09327,680
Msadco.dll2.53.6307.029-Nov-200617:31151,824
Msadcs.dll2.53.6307.029-Nov-200617:3157,616
Msado15.dll2.53.6307.010-Jan-200719:09487,424
Msadomd.dll2.53.6307.010-Jan-200719:09172,066
Msadox.dll2.53.6307.010-Jan-200719:09188,449
Msdaprst.dll2.53.6307.010-Jan-200719:09204,800
Msdaps.dll2.53.6307.029-Nov-200617:31192,784
Msjro.dll2.53.6307.010-Jan-200719:0994,240
Odbc32.dll3.520.6307.010-Jan-200719:09212,992
Odbcbcp.dll3.70.11.4628-Oct-200321:4424,848
Odbccp32.dll3.520.6307.029-Nov-200617:31102,672
Odbcji32.dll4.0.6307.029-Nov-200617:3153,520
Odbcjt32.dll4.0.6307.029-Nov-200617:31278,800
Oddbse32.dll4.0.6307.029-Nov-200617:3120,752
Odexl32.dll4.0.6307.029-Nov-200617:3120,752
Odfox32.dll4.0.6307.029-Nov-200617:3120,752
Odpdx32.dll4.0.6307.029-Nov-200617:3120,752
Odtext32.dll4.0.6307.029-Nov-200617:3120,752
Oledb32.dll2.53.6307.010-Jan-200719:09483,328
Sqlsrv32.dll3.70.11.4628-Oct-200321:44524,560
Datasource.xmlN/A10-Jan-200719:0925,132
Sqlse.rll1.4.17.005-Jan-200716:4954,272
Sqlstpcustomdll.dll1.4.17.010-Jan-200719:092,290,688
Sqlstpcustomdll.rll1.4.17.005-Jan-200716:4912,288

Microsoft Data Access Components 2.7 Service Pack 1:

File NameVersionDateTimeSize
Sprecovr.exe6.2.29.023-Dec-200600:0129,408
Spupdsvc.exe6.2.29.023-Dec-200600:0122,752
Dbnetlib.dll2000.81.9054.023-Dec-200600:0161,440
Msadce.dll2.71.9054.023-Dec-200600:01307,200
Msadcf.dll2.71.9054.023-Dec-200600:0157,344
Msadco.dll2.71.9054.023-Dec-200600:01135,168
Msadcs.dll2.71.9054.023-Dec-200600:0153,248
Msadds.dll2.71.9054.023-Dec-200600:01147,456
Msado15.dll2.71.9054.023-Dec-200600:01491,520
Msadomd.dll2.71.9054.023-Dec-200600:01159,744
Msadox.dll2.71.9054.023-Dec-200600:01180,224
Msadrh15.dll2.71.9054.023-Dec-200600:0153,248
Msdaora.dll2.71.9054.023-Dec-200600:01221,184
Msdaprst.dll2.71.9054.023-Dec-200600:01180,224
Msdaps.dll2.71.9054.023-Dec-200600:01188,416
Msdarem.dll2.71.9054.023-Dec-200600:01110,592
Msdart.dll2.71.9054.023-Dec-200600:01126,976
Msdasql.dll2.71.9054.023-Dec-200600:01303,104
Msdfmap.dll2.71.9054.023-Dec-200600:0132,768
Msjro.dll2.71.9054.023-Dec-200600:0190,112
Msorcl32.dll2.573.9054.023-Dec-200600:01131,072
Odbc32.dll3.520.9054.023-Dec-200600:01204,800
Odbcbcp.dll2000.81.9054.023-Dec-200600:0124,576
Odbccp32.dll3.520.9054.023-Dec-200600:0198,304
Odbccr32.dll3.520.9054.023-Dec-200600:0161,440
Odbccu32.dll3.520.9054.023-Dec-200600:0161,440
Oledb32.dll2.71.9054.023-Dec-200600:01413,696
Sqloledb.dll2000.81.9054.023-Dec-200600:01471,040
Sqlsrv32.dll2000.81.9054.023-Dec-200600:01385,024
Sqlxmlx.dll2000.81.9054.023-Dec-200600:01200,704
Datasource.xmlN/A23-Dec-200600:0126,546
Sqlse.rll1.4.17.023-Dec-200600:0154,272
Sqlstpcustomdll.dll1.4.17.023-Dec-200600:012,290,688
Sqlstpcustomdll.rll1.4.17.023-Dec-200600:0112,288

Microsoft Data Access Components 2.8:

File NameVersionDateTimeSize
Sprecovr.exe6.2.29.023-Dec-200602:5629,408
Spupdsvc.exe6.2.29.023-Dec-200602:5622,752
Dbnetlib.dll2000.85.1064.023-Dec-200602:5573,728
Dbnmpntw.dll2000.85.1064.023-Dec-200602:5528,672
Msadce.dll2.80.1064.023-Dec-200602:55315,392
Msadco.dll2.80.1064.023-Dec-200602:55135,168
Msadcs.dll2.80.1064.023-Dec-200602:5549,152
Msadds.dll2.80.1064.023-Dec-200602:55147,456
Msado15.dll2.80.1064.023-Dec-200602:55507,904
Msadomd.dll2.80.1064.023-Dec-200602:55163,840
Msadox.dll2.80.1064.023-Dec-200602:55184,320
Msadrh15.dll2.80.1064.023-Dec-200602:5553,248
Msdaora.dll2.80.1064.023-Dec-200602:55225,280
Msdaprst.dll2.80.1064.023-Dec-200602:55192,512
Msdart.dll2.80.1064.023-Dec-200602:55147,456
Msdasql.dll2.80.1064.023-Dec-200602:55303,104
Msjro.dll2.80.1064.023-Dec-200602:5590,112
Msorcl32.dll2.575.1064.023-Dec-200602:55139,264
Odbc32.dll3.525.1064.023-Dec-200602:55221,184
Odbcbcp.dll2000.85.1064.023-Dec-200602:5524,576
Oledb32.dll2.80.1064.023-Dec-200602:55442,368
Sqloledb.dll2000.85.1064.023-Dec-200602:55503,808
Sqlsrv32.dll2000.85.1064.023-Dec-200602:55401,408
Sqlxmlx.dll2000.85.1064.023-Dec-200602:55208,896
Datasource.xmlN/A23-Dec-200602:5525,364
Sqlse.rll1.4.17.023-Dec-200602:5654,272
Sqlstpcustomdll.dll1.4.17.023-Dec-200602:562,290,688
Sqlstpcustomdll.rll1.4.17.023-Dec-200602:5612,288

Microsoft Data Access Components 2.8 Service Pack 1:

File NameVersionDateTimeSize
Sprecovr.exe6.2.29.005-Jan-200723:3329,408
Spupdsvc.exe6.2.29.005-Jan-200723:3322,752
Msadco.dll2.81.1128.005-Jan-200723:40143,360
Msado15.dll2.81.1128.005-Jan-200723:40524,288
Msadomd.dll2.81.1128.005-Jan-200723:40180,224
Msadox.dll2.81.1128.005-Jan-200723:40200,704
Msdasql.dll2.81.1128.005-Jan-200723:40307,200
Msjro.dll2.81.1128.005-Jan-200723:40102,400
Odbcbcp.dll2000.85.1128.005-Jan-200723:4024,576
Sqloledb.dll2000.85.1128.005-Jan-200723:40520,192
Sqlsrv32.dll2000.85.1128.005-Jan-200723:40438,272
Datasource.xmlN/A05-Jan-200723:4022,816
Sqlse.rll1.4.17.005-Jan-200721:2854,272
Sqlstpcustomdll.dll1.4.17.005-Jan-200723:402,290,688
Sqlstpcustomdll.rll1.4.17.005-Jan-200721:2812,288

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 can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.

  • File Version Verification

Note 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. Start, and then click Search.
  2. Search Results pane, click All files and folders under Search Companion.
  3. All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
  4. 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. 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.
  6. Registry Key Verification

You may also be able to verify the files that this security update has installed by reviewing the following registry keys.

Microsoft Data Access Components 2.5 Service Pack 3:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\DataAccess\MDAC25\SP3\KB927779\Filelist

Microsoft Data Access Components 2.7 Service Pack 1:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\DataAccess\MDAC27\SP1\KB927779\Filelist

Microsoft Data Access Components 2.8:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\DataAccess\MDAC28\SP0\KB927779\Filelist

Microsoft Data Access Components 2.8 Service Pack 1:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\DataAccess\MDAC28\SP1\KB927779\Filelist

Note This registry keys may not contain a complete list of installed files. Also, this registry key may not be created correctly when an administrator or an OEM integrates or slipstreams the 927779 security update into the Windows installation source files.

Windows XP (all versions)

Prerequisites
This security update requires Microsoft Windows XP Service Pack 2. For more information, see Microsoft Knowledge Base Article 322389.

Inclusion in Future Service Packs:
The update for this issue will be included in a future Service Pack or Update Rollup.

Installation Information

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.
/extract[:path] Extracts files without starting the Setup program
/ER Enables extended error reporting
/verbose Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

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

Deployment Information

Note If you are unsure of the version of MDAC you are running, install the Component Checker.

To install the security update without any user intervention, use the following command at a command prompt for Microsoft Windows XP.

Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:

WindowsXP-KB927779-x86-enu /quiet

Note Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the following KB927779.log file for any failure messages when they use this switch.

To install the security update without forcing the system to restart, use the following command at a command prompt for Windows XP.

Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:

WindowsXP-KB927779-x86-enu /norestart

For information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.

Restart Requirement

This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.

Removal Information

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

System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB927779$\Spuninst folder.

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

File Information

The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:

File NameVersionDateTimeSizeFolder
Msado15.dll2.81.1128.026-Dec-200613:07536,576SP2GDR
Msadomd.dll2.81.1128.026-Dec-200613:07180,224SP2GDR
Msadox.dll2.81.1128.026-Dec-200613:07200,704SP2GDR
Msjro.dll2.81.1128.026-Dec-200613:07102,400SP2GDR
Msado15.dll2.81.1128.026-Dec-200613:18536,576SP2QFE
Msadomd.dll2.81.1128.026-Dec-200613:18180,224SP2QFE
Msadox.dll2.81.1128.026-Dec-200613:18200,704SP2QFE
Msjro.dll2.81.1128.026-Dec-200613:18102,400SP2QFE

Notes When you install these security updates, 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.

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

For more information about the Update.exe installer, visit the Microsoft TechNet Web site.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

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 can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.

  • File Version Verification

Note 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.
    1. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    2. 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.
  3. 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.
  4. Registry Key Verification

You may also be able to verify the files that this security update has installed by reviewing the following registry keys.

Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB927779\Filelist

Note These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly if an administrator or an OEM integrates or slipstreams the 927779 security update into the Windows installation source files.

Windows Server 2003 (all versions)

Prerequisites
This security update requires Windows Server 2003.

Inclusion in Future Service Packs
The update for this issue will be included in future Service Pack or Update Rollup.

Installation Information

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 forces other applications to close at shutdown without saving open files first.
/warnrestart[:x] Displays 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 uninstallation.
/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.

Deployment Information

To install the security update without any user intervention, use the following command at a command prompt for Windows Server 2003:

WindowsServer2003-KB927779-x86-enu /quiet

Note Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB927779.log file for any failure messages when they use this switch.

To install the security update without forcing the system to restart, use the following command at a command prompt for Windows Server 2003:

WindowsServer2003-KB927779-x86-enu /norestart

For information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.

Restart Requirement

This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.

Removal Information

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

System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB927779$\Spuninst folder.

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 forces other applications to close at shutdown without saving open files first.
/warnrestart[:x] Displays 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.

File Information

The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition; Windows Small Business Server 2003:

File NameVersionDateTimeSizeFolder
Msado15.dll2.80.1064.019-Dec-200609:37520,192RTMGDR
Msadomd.dll2.80.1064.019-Dec-200609:20163,840RTMGDR
Msadox.dll2.80.1064.019-Dec-200609:20184,320RTMGDR
Msjro.dll2.80.1064.019-Dec-200609:2090,112RTMGDR
Msado15.dll2.80.1064.019-Dec-200610:01520,192RTMQFE
Msadomd.dll2.80.1064.019-Dec-200609:49163,840RTMQFE
Msadox.dll2.80.1064.019-Dec-200609:49184,320RTMQFE
Msjro.dll2.80.1064.019-Dec-200609:4990,112RTMQFE

Windows Server 2003, Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems:

File NameVersionDateTimeSizeCPUFolder
Msado15.dll2.80.1064.019-Dec-200608:551,384,448IA-64RTMGDR
Msadomd.dll2.80.1064.019-Dec-200608:55483,328IA-64RTMGDR
Msadox.dll2.80.1064.019-Dec-200608:55536,576IA-64RTMGDR
Wmsado15.dll2.80.1064.019-Dec-200609:38520,192x86RTMQFE\WOW
Wmsadomd.dll2.80.1064.019-Dec-200609:20163,840x86RTMQFE\WOW
Wmsadox.dll2.80.1064.019-Dec-200609:20184,320x86RTMQFE\WOW
Wmsjro.dll2.80.1064.019-Dec-200609:2090,112x86RTMQFE\WOW
Msado15.dll2.80.1064.019-Dec-200609:201,384,448IA-64RTMQFE
Msadomd.dll2.80.1064.019-Dec-200609:20483,328IA-64RTMQFE
Msadox.dll2.80.1064.019-Dec-200609:20536,576IA-64RTMQFE
Wmsado15.dll2.80.1064.019-Dec-200610:01520,192x86RTMQFE\WOW
Wmsadomd.dll2.80.1064.019-Dec-200609:49163,840x86RTMQFE\WOW
Wmsadox.dll2.80.1064.019-Dec-200609:49184,320x86RTMQFE\WOW
Wmsjro.dll2.80.1064.019-Dec-200609:4990,112x86RTMQFE\WOW

Notes When you install these security updates, 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.

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

For more information about this behavior, see Microsoft Knowledge Base Article 824994.

For more information about the Update.exe installer, visit the Microsoft TechNet Web site.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

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 frequently asked question, “Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine whether this update is required?” in the section, Frequently Asked Questions (FAQ) Related to This Security Update, earlier in this bulletin.

  • File Version Verification

    Note 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.
  • Registry Key Verification

    You may also be able to verify the files that this security update has installed by reviewing the following registry keys.

    Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition; Windows Small Business Server 2003; Windows Server 2003, Enterprise Edition for Itanium-based Systems; and Windows Server 2003, Datacenter Edition for Itanium-based Systems:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP1\KB927779\Filelist

    Note This registry key may not contain a complete list of installed files. Also, this registry key may not be created correctly if an administrator or an OEM integrates or slipstreams the 927779 security update into the Windows installation source files.

Other Information

Acknowledgments

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

  • FrSIRT for originally reporting the Microsoft Windows MDAC ActiveX Vulnerability (CVE-2006-5559).

Obtaining Other Security Updates:

Updates for other security issues are available at the following locations:

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.

Security Resources:

Software Update Services:

By using Microsoft Software Update Services (SUS), administrators can quickly and reliably deploy the latest critical updates and security updates to Windows 2000 and Windows Server 2003-based servers, and to desktop systems that are running Windows 2000 Professional or Windows XP Professional.

For more information about how to deploy security updates by using Software Update Services, visit the Software Update Services Web site.

Windows Server Update Services:

By using Windows Server Update Services (WSUS), administrators can quickly and reliably deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 onto Windows 2000 and later operating systems.

For more information about how to deploy security updates using Windows Server Update Services, visit the Windows Server Update Services Web site.

Systems Management Server:

Microsoft Systems Management Server (SMS) delivers a highly configurable enterprise solution for managing updates. By using SMS, administrators can identify Windows-based systems that require security updates and can perform controlled deployment of these updates throughout the enterprise with minimal disruption to end users. For more information about how administrators can use SMS 2003 to deploy security updates, visit the SMS 2003 Security Patch Management Web site. SMS 2.0 users can also use Software Updates Service Feature Pack to help deploy security updates. For information about SMS, visit the SMS Web site.

Note SMS uses the Microsoft Baseline Security Analyzer, the Microsoft Office Detection Tool, and the Enterprise Update Scan Tool to provide broad support for security bulletin update detection and deployment. Some software updates may not be detected by these tools. Administrators can use the inventory capabilities of the SMS in these cases to target updates to specific systems. For more information about this procedure, visit the following Web site. Some security updates require administrative rights following a restart of the system. Administrators can use the Elevated Rights Deployment Tool (available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 Administration Feature Pack) to install these updates.

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 (February 13, 2007): Bulletin published.

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

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