SecurityvulnsSECURITYVULNS:DOC:12167Microsoft Security Bulletin MS06-014 Vulnerability in the Microsoft Data Access Components (MDAC) Function Could Allow Code Execution (911562)
Microsoft Security Bulletin MS06-014
Vulnerability in the Microsoft Data Access Components (MDAC) Function Could Allow Code Execution (911562)
Published: April 11, 2006
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 at the earliest opportunity.
Security Update Replacement: None
Caveats: None
Tested Software and Security Update Download Locations:
Affected Software:
•
Microsoft Windows XP Service Pack 1 running Microsoft Data Access Components 2.7 Service Pack 1 - Download the update
•
Microsoft Windows XP Service Pack 2 running Microsoft Data Access Components 2.8 Service Pack 1 – Download the update
•
Microsoft Windows XP Professional x64 Edition running Microsoft Data Access Components 2.8 Service Pack 2 - Download the update
•
Microsoft Windows Server 2003 running Microsoft Data Access Components 2.8 - Download the update
•
Microsoft Windows Server 2003 Service Pack 1 running Microsoft Data Access Components 2.8 Service Pack 2 – Download the update
•
Microsoft Windows Server 2003 for Itanium-based Systems running Microsoft Data Access Components 2.8 - Download the update
•
Microsoft Windows Server 2003 with SP1 for Itanium-based Systems running Microsoft Data Access Components 2.8 Service Pack 2 - Download the update
•
Microsoft Windows Server 2003 x64 Edition running Microsoft Data Access Components 2.8 Service Pack 2 - Download the update
•
Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE), and Microsoft Windows Millennium Edition (ME) – Review the FAQ section of this bulletin for details about these operating systems.
Tested Microsoft Windows Components:
Affected Components:
•
Windows 2000 Service Pack 4 with Microsoft Data Access Components 2.5 Service Pack 3 installed - Download the update
•
Windows 2000 Service Pack 4 with Microsoft Data Access Components 2.7 Service Pack 1 installed- Download the update
•
Windows 2000 Service Pack 4 with Microsoft Data Access Components 2.8 installed - Download the update
•
Windows 2000 Service Pack 4 with Microsoft Data Access Components 2.8 Service Pack 1 installed - Download the update
•
Windows XP Service Pack 1 with Microsoft Data Access Components 2.8 installed - 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.
Note The security updates for Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 also apply to Microsoft Windows Server 2003 R2.
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.
Top of sectionTop of section
General Information
Executive Summary
Executive Summary:
This update resolves a newly-discovered, privately-reported 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 Identifiers Impact of Vulnerability Windows 98,Windows 98 SE and Windows ME Windows 2000 Service Pack 4 Windows XP Service Pack 1 and Windows XP Service Pack 2 Windows Server 2003 and Windows Server 2003 Service Pack 1
Microsoft Windows MDAC Vulnerability - CVE-2006-0003
Remote Code Execution
Critical
Critical
Critical
Moderate
Note All versions of Microsoft Data Access Components (MDAC) for the affected operating system have the same severity rating of Critical.
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 The severity ratings for non-x86 operating system versions map to the x86 operating systems versions as follows:
•
The Microsoft Windows XP Professional x64 Edition severity rating is the same as the Windows XP Service Pack 2 severity rating.
•
The Microsoft Windows Server 2003 R2 Systems severity rating is the same as the Windows Server 2003 severity rating.
•
The Microsoft Windows Server 2003 for Itanium-based Systems severity rating is the same as the Windows Server 2003 severity rating.
•
The Microsoft Windows Server 2003 with SP1 for Itanium-based Systems severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating.
•
The Microsoft Windows Server 2003 x64 Edition severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating.
Top of sectionTop of section
Frequently asked questions (FAQ) related to this security update
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. Why do I need to upgrade to version 2.8 Service Pack 1 of Microsoft Data Access Components?
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.
Does this update contain any changes to functionality?
Yes. The RDS.Dataspace ActiveX control that is provided in MDAC contains additional restrictions that affect the way that it interacts within Internet Explorer. These restrictions may interfere with the normal operation of some applications if those applications load the RDS.Database ActiveX control within Internet Explorer.
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 malicious 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.
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 additional support for Windows NT 4.0 Service Pack 6a and Windows 2000 Service Pack 3 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.
Are Windows 98, Windows 98 Second Edition, or Windows Millennium Edition critically affected by one or more of the vulnerabilities that are addressed in this security bulletin?
Yes. Windows 98, Windows 98 Second Edition, and Windows Millennium Edition are critically affected by this vulnerability. These security updates are available for download from the Windows Update Web site. For more information about severity ratings, visit the following Web site.
Note Updates for localized versions of Microsoft Windows Millennium Edition that are not supported by Windows Update are available for download at the following download locations:
•
Slovenian – Download the update
•
Slovakian – Download the update
Can I use the Microsoft Baseline Security Analyzer (MBSA) 1.2.1 to determine whether this update is required?
Yes. MBSA 1.2.1 will determine whether this update is required for Windows XP Service Pack 2 and Windows Server 2003 Service Pack 1.
MBSA 1.2.1 does not support the detection of MDAC on Windows 2000 Service Pack 4, on Windows XP Service Pack 1, and on Windows Server 2003. For more information about MBSA, visit the MBSA Web site. For more information about the programs that MBSA 1.2.1 currently does not detect, see Microsoft Knowledge Base Article 306460. However, Microsoft has developed a version of the Enterprise Scan Tool (EST) that will help customers determine whether the security updates provided in this security bulletin are required. For more information, see the "Can I use a version of the Enterprise Scan Tool (EST) to determine whether this update is required?" question.
Can I use the Microsoft Baseline Security Analyzer (MBSA) 2.0 to determine whether this update is required?
Yes. MBSA 2.0 will determine whether this update is required. MBSA 2.0 can detect security updates for products that Microsoft Update supports. For more information about MBSA, visit the MBSA Web site.
What is the Enterprise Update Scanning 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 Scan Tool (EST) and is designed for enterprise administrators. When a version of the Enterprise Update Scanning 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 Scanning Tool (EST) to determine whether this update is required?
Yes. Microsoft has created a version of the EST that will determine if you have to apply this update. For download links and more information about the version of the EST that is being released this month, see the following Microsoft Web site. SMS customers should review the "Can I use Systems Management Server (SMS) to determine whether this update is required?" FAQ for more information about SMS and EST.
Can I use Systems Management Server (SMS) to determine whether this update is required?
Yes. SMS can help detect and deploy this security update.
SMS can use the SMS Software Update Services (SUS) Feature Pack to detect security updates. The SMS SUS Feature Pack includes the Security Update Inventory Tool (SUIT). For more information about the Security Update Inventory Tool, visit the following Microsoft Web site. For more information about the limitations of the Security Update Inventory Tool, see Microsoft Knowledge Base Article 306460.
The SMS SUS Feature Pack also includes the Microsoft Office Inventory Tool to detect for required updates for Microsoft Office applications.
SMS can use the SMS 2003 Inventory Tool for Microsoft Updates 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 Inventory Tool for Microsoft Updates, visit the following Microsoft Web site.
SMS 2.0 and SMS 2003 customers who do not use the SMS 2003 Inventory Tool for Microsoft Updates must download and deploy an updated version of the Extended Security Update Inventory Tool to receive full detection and deployment for this update.
For more information about SMS, visit the SMS Web site.
Top of sectionTop of section
Vulnerability Details
Microsoft Windows MDAC Vulnerability - CVE-2006-0003:
A remote code execution vulnerability exists in the RDS.Dataspace 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 Vulnerability - CVE-2006-0003:
•
In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to attempt to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site. It could also be possible to display malicious Web content by using banner advertisements or by using other methods to deliver Web content to affected systems.
•
An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
•
By default, Internet Explorer on Windows Server 2003 runs in a restricted mode that is known as Enhanced Security Configuration. This mode mitigates this vulnerability in the e-mail vector because reading e-mail messages in plain text is the default configuration for Outlook Express. See the FAQ section of this security update for more information about Internet Explorer Enhanced Security Configuration.
Top of sectionTop of section
Workarounds for Microsoft Windows MDAC Vulnerability - CVE-2006-0003:
Microsoft has tested the following workarounds. While 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.
Disable the RDS.Dataspace ActiveX control from running within Internet Explorer
Disable attempts to instantiate the RDS.Dataspace ActiveX control in Internet Explorer by setting the kill bit for the control.
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.
For example, to set the kill bit for a CLSID for this object, paste the following text in a text editor such as Notepad. Then, save the file by using the .reg file name extension.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{BD96C556-65A3-11D0-983A-00C04FC29E36}]"Compatibility Flags"=dword: 00000400
Note For more information about how to prevent a control from running in Internet Explorer, see Microsoft Knowledge Base Article 240797. Follow the procedure that this article provides to create a Compatibility Flags value in the registry. By doing this, you will prevent the RDS.Dataspace ActiveX control from being instantiated in Internet Explorer.
Impact of Workaround: Any Web-based application that requires the RDS control to be instantiated within Internet Explorer will no longer function correctly.
Top of sectionTop of section
Set Internet and Local intranet security zone settings to “High” to prompt before running ActiveX controls 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:
On the Internet Explorer Tools menu, click Internet Options.
In the Internet Options dialog box, click the Security tab, and then click the Internet icon.
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.
Repeat steps 1 through 3 for the Local intranet security zone by clicking on the Local intranet icon.
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: User will be prompted prior to running ActiveX controls unless the Web site is in the user’s list of trusted sites.
Top of sectionTop of section
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 settings to prompt before running ActiveX controls or disable ActiveX controls in the Internet and Local intranet security zone. To do this, follow these steps:
On the Internet Explorer Tools menu, click Internet Options.
In the Internet Options dialog box, click the Security tab, and then click the Internet icon.
Click Custom Level.
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.
Click Local intranet, and then click Custom Level.
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.
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.
Top of sectionTop of section
Top of sectionTop of section
FAQ for Microsoft Windows MDAC Vulnerability - CVE-2006-0003:
What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could remotely take complete control of an affected system.
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.
What causes the vulnerability?
Under certain conditions, the RDS.Dataspace ActiveX control fails to ensure that it interacts safely when it is hosted on a Web page.
What is Remote Data Services (RDS)?
Remote Data Service (RDS) is a feature of ADO. You can use RDS to move data from a server to a client application or to a Web page, to manipulate the data on the client, and to return updates to the server in a single round trip.
Who could exploit the vulnerability?
An attacker could create an e-mail message that is specially crafted to try to exploit this vulnerability. An attacker could exploit the vulnerability by sending this specially crafted e-mail message to a user of a server that is running an affected software application. An attacker could then persuade the user to click a link in the e-mail message. In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to attempt to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site. It could also be possible to display malicious 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 reading e-mail messages or is visiting Web sites for any malicious action to occur. Therefore, any systems where e-mail messages are read or where Internet Explorer is used frequently, such as workstations or terminal servers, are at the most risk from this vulnerability.
What does the update do?
The update removes the vulnerability by applying additional restrictions to the behavior of the RDS.Dataspace ActiveX control when it is hosted on a Web page.
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.
Top of sectionTop of section
Top of sectionTop of section
Top of sectionTop of section
Security Update Information
Affected Software:
For information about the specific security update for your affected software, click the appropriate link:
Windows Server 2003 (all versions)
Prerequisites
This security update requires Windows Server 2003 or Windows Server 2003 Service Pack 1.
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
Switch Description
/help
Displays the command-line options
Setup Modes
/passive
Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet
Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart
Does not restart when installation has completed
/forcerestart
Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]
Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart
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.
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 Server 2003:
Windowsserver2003-kb911562-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 KB911562.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-kb911562-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%\$NTUninstallKB911562$\Spuninst folder.
Supported Spuninst.exe Switches
Switch Description
/help
Displays the command-line options
Setup Modes
/passive
Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet
Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart
Does not restart when installation has completed
/forcerestart
Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]
Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart
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, Datacenter Edition; Windows Server 2003, Enterprise Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; and Windows Server 2003, Datacenter Edition with SP1;. ; Windows Server 2003 R2, Web Edition; Windows Server 2003 R2, Standard Edition; Windows Server 2003 R2, Datacenter Edition; Windows Server 2003 R2, Enterprise Edition; Windows Small Business Server 2003 R2:
File Name Version Date Time Size CPU Folder
Msadco.dll
2.80.1062.0
22-Feb-2006
00:47
135,168
x86
RTMGDR
Msadco.dll
2.80.1062.0
22-Feb-2006
01:17
135,168
x86
RTMQFE
Msadco.dll
2.82.2644.0
22-Feb-2006
20:52
147,456
x86
SP1GDR
Msadco.dll
2.82.2644.0
22-Feb-2006
20:47
147,456
x86
SP1QFE
Windows Server, 2003 Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; and Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems:
File Name Version Date Time Size CPU Folder
Msadco.dll
2.80.1062.0
22-Feb-2006
21:14
434,176
IA-64
RTMGDR
Wmsadco.dll
2.80.1062.0
22-Feb-2006
21:14
135,168
x86
RTMGDR\WOW
Msadco.dll
2.80.1062.0
22-Feb-2006
21:14
434,176
IA-64
RTMQFE
Wmsadco.dll
2.80.1062.0
22-Feb-2006
21:14
135,168
x86
RTMQFE\WOW
Msadco.dll
2.82.2644.0
22-Feb-2006
21:20
483,328
IA-64
SP1GDR
Wmsadco.dll
2.82.2644.0
22-Feb-2006
21:20
147,456
x86
SP1GDR\WOW
Msadco.dll
2.82.2644.0
22-Feb-2006
21:14
483,328
IA-64
SP1QFE
Wmsadco.dll
2.82.2644.0
22-Feb-2006
21:14
147,456
x86
SP1QFE\WOW
Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition:
File Name Version Date Time Size CPU Folder
Msadco.dll
2.82.2644.0
22-Feb-2006
21:18
233,472
x64
SP1GDR
Wmsadco.dll
2.82.2644.0
22-Feb-2006
21:18
147,456
x86
SP1GDR\WOW
Msadco.dll
2.82.2644.0
22-Feb-2006
21:14
233,472
x64
SP1QFE
Wmsadco.dll
2.82.2644.0
22-Feb-2006
21:14
147,456
x86
SP1QFE\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 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.
Click Start, and then click Search.
In the Search Results pane, click All files and folders under Search Companion.
In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
On the Version tab, determine the version of the file that is installed on your 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\SP2\KB911562\Filelist
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, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; Windows Server 2003, Datacenter Edition with SP1, Windows Server 2003 R2, Web Edition; Windows Server 2003 R2, Standard Edition; Windows Server 2003 R2, Datacenter Edition; Windows Server 2003 R2, Enterprise Edition; Windows Small Business Server 2003 R2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP2\KB911562\Filelist
Note This registry keys may not contain a complete list of installed files. Also, this registry keys may not be created correctly if an administrator or an OEM integrates or slipstreams the 911562 security update into the Windows installation source files.
Top of sectionTop of section
Windows XP (all versions)
Prerequisites
This security update requires Microsoft Windows XP Service Pack 1 or a later version. 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
Switch Description
/help
Displays the command-line options
Setup Modes
/passive
Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet
Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart
Does not restart when installation has completed
/forcerestart
Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]
Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart
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:
Windowsxp-kb911562-x86-enu /quiet
or
MDAC28-KB911562-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 Windowsxp-kb911562-x86-XXX.log or MDAC28-KB911562-x86-XXX.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 XP:
Windowsxp-kb911562-x86-enu /norestart
or
MDAC28-KB911562-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%\$NTUninstallKB911562$\Spuninst folder.
Supported Spuninst.exe Switches
Switch Description
/help
Displays the command-line options
Setup Modes
/passive
Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet
Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart
Does not restart when installation has completed
/forcerestart
Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]
Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart
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 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, 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 Name Version Date Time Size CPU Folder
Msadco.dll
2.71.9053.0
25-Feb-2006
01:14
135,168
x86
SP1QFE
Msadco.dll
2.81.1124.0
25-Feb-2006
01:05
143,360
x86
SP2GDR
Msadco.dll
2.81.1124.0
25-Feb-2006
01:03
143,360
x86
SP2QFE
Windows XP Professional x64:
File Name Version Date Time Size CPU Folder
Msadco.dll
2.82.2644.0
22-Feb-2006
21:18
233,472
x64
SP1GDR
Wmsadco.dll
2.82.2644.0
22-Feb-2006
21:18
147,456
x86
SP1GDR\WOW
Msadco.dll
2.82.2644.0
22-Feb-2006
21:14
233,472
x64
SP1QFE
Wmsadco.dll
2.82.2644.0
22-Feb-2006
21:14
147,456
x86
SP1QFE\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 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.
Click Start, and then click Search.
In the Search Results pane, click All files and folders under Search Companion.
In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
On the Version tab, determine the version of the file that is installed on your 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.
For Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB911562\Filelist
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\KB911562\Filelist
For Windows XP Professional x64 Edition:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP2\ KB911562Filelist
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 911562 security update into the Windows installation source files.
Top of sectionTop of section
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
Switch Description
/help
Displays the command-line options
Setup Modes
/passive
Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet
Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart
Does not restart when installation has completed
/forcerestart
Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]
Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart
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:
MDAC253-KB911562-x86-enu /quiet
or
MDAC271-KB911562-x86-enu /quiet
or
MDAC28-KB911562-x86-enu /quiet
or
MDAC281-KB911562-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-KB911562-x86-XXX.log, MDAC271-KB911562-x86-XXX.log, MDAC28-KB911562-XXX.log or MDAC281-KB911562-XXX.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:
MDAC253-KB911562-x86-enu / norestart
or
MDAC271-KB911562-x86-enu / norestart
or
MDAC28-KB911562-x86-enu / norestart
or
MDAC281-KB911562-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-KB911562-x86-XXX$\Spuninst, %Windir%\$SQLUninstallMDAC27SP1-KB911562-x86-XXX$\Spuninst, %Windir%\$SQLUninstallMDAC28-KB911562-x86-XXX$\Spuninst, or %Windir%\$SQLUninstallMDAC28SP1-KB911562-x86-XXX$\Spuninst
Supported Spuninst.exe Switches
Switch Description
/help
Displays the command-line options
Setup Modes
/passive
Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet
Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart
Does not restart when installation has completed
/forcerestart
Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]
Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart
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 Name Version Date Time Size CPU
Sprecovr.exe
6.2.29.0
17-Feb-2006
23:05
29,408
x86
Spupdsvc.exe
6.2.29.0
17-Feb-2006
23:05
22,752
x86
Msadce.dll
2.53.6306.0
21-Feb-2006
19:57
327,680
x86
Msadco.dll
2.53.6306.0
21-Feb-2006
17:58
151,824
x86
Msadcs.dll
2.53.6306.0
21-Feb-2006
17:58
57,616
x86
Msado15.dll
2.53.6306.0
21-Feb-2006
19:57
487,424
x86
Msdaprst.dll
2.53.6306.0
21-Feb-2006
19:57
204,800
x86
Msdaps.dll
2.53.6306.0
21-Feb-2006
17:58
192,784
x86
Odbc32.dll
3.520.6306.0
21-Feb-2006
19:57
212,992
x86
Odbcbcp.dll
3.70.11.46
28-Oct-2003
21:44
24,848
x86
Odbccp32.dll
3.520.6306.0
21-Feb-2006
17:58
102,672
x86
Odbcji32.dll
4.0.6306.0
21-Feb-2006
17:58
53,520
x86
Odbcjt32.dll
4.0.6306.0
21-Feb-2006
17:58
278,800
x86
Oddbse32.dll
4.0.6306.0
21-Feb-2006
17:58
20,752
x86
Odexl32.dll
4.0.6306.0
21-Feb-2006
17:58
20,752
x86
Odfox32.dll
4.0.6306.0
21-Feb-2006
17:58
20,752
x86
Odpdx32.dll
4.0.6306.0
21-Feb-2006
17:58
20,752
x86
Odtext32.dll
4.0.6306.0
21-Feb-2006
17:58
20,752
x86
Oledb32.dll
2.53.6306.0
21-Feb-2006
19:57
483,328
x86
Sqlsrv32.dll
3.70.11.46
28-Oct-2003
21:44
524,560
x86
Datasource.xml
21-Feb-2006
19:57
24,532
Sqlse.rll
1.1.2022.0
17-Feb-2006
23:04
45,056
Sqlstpcustomdll.dll
1.1.2022.0
21-Feb-2006
19:57
1,843,712
x86
Sqlstpcustomdll.rll
1.1.2022.0
17-Feb-2006
23:04
12,288
Microsoft Data Access Components 2.7 Service Pack 1:
File Name Version Date Time Size CPU
Sprecovr.exe
6.2.29.0
18-Feb-2006
06:51
29,408
x86
Spupdsvc.exe
6.2.29.0
18-Feb-2006
06:51
22,752
x86
Dbnetlib.dll
2000.81.9053.0
25-Feb-2006
07:57
61,440
x86
Msadce.dll
2.71.9053.0
25-Feb-2006
07:57
307,200
x86
Msadcf.dll
2.71.9053.0
25-Feb-2006
07:57
57,344
x86
Msadco.dll
2.71.9053.0
25-Feb-2006
07:57
135,168
x86
Msadcs.dll
2.71.9053.0
25-Feb-2006
07:57
53,248
x86
Msadds.dll
2.71.9053.0
25-Feb-2006
07:57
147,456
x86
Msado15.dll
2.71.9053.0
25-Feb-2006
07:57
491,520
x86
Msadomd.dll
2.71.9053.0
25-Feb-2006
07:57
159,744
x86
Msadox.dll
2.71.9053.0
25-Feb-2006
07:57
180,224
x86
Msadrh15.dll
2.71.9053.0
25-Feb-2006
07:57
53,248
x86
Msdaora.dll
2.71.9053.0
25-Feb-2006
07:57
221,184
x86
Msdaprst.dll
2.71.9053.0
25-Feb-2006
07:57
180,224
x86
Msdaps.dll
2.71.9053.0
25-Feb-2006
07:57
188,416
x86
Msdarem.dll
2.71.9053.0
25-Feb-2006
07:57
110,592
x86
Msdart.dll
2.71.9053.0
25-Feb-2006
07:57
126,976
x86
Msdasql.dll
2.71.9053.0
25-Feb-2006
07:57
303,104
x86
Msdfmap.dll
2.71.9053.0
25-Feb-2006
07:57
32,768
x86
Msjro.dll
2.71.9053.0
25-Feb-2006
07:57
90,112
x86
Msorcl32.dll
2.573.9053.0
25-Feb-2006
07:57
131,072
x86
Odbc32.dll
3.520.9053.0
25-Feb-2006
07:57
204,800
x86
Odbcbcp.dll
2000.81.9053.0
25-Feb-2006
07:57
24,576
x86
Odbccp32.dll
3.520.9053.0
25-Feb-2006
07:57
98,304
x86
Odbccr32.dll
3.520.9053.0
25-Feb-2006
07:57
61,440
x86
Odbccu32.dll
3.520.9053.0
25-Feb-2006
07:57
61,440
x86
Oledb32.dll
2.71.9053.0
25-Feb-2006
07:57
417,792
x86
Sqloledb.dll
2000.81.9053.0
25-Feb-2006
07:57
471,040
x86
Sqlsrv32.dll
2000.81.9053.0
25-Feb-2006
07:57
385,024
x86
Sqlxmlx.dll
2000.81.9053.0
25-Feb-2006
07:57
200,704
x86
Datasource.xml
25-Feb-2006
07:57
26,546
Sqlse.rll
1.1.2022.0
18-Feb-2006
06:49
45,056
Sqlstpcustomdll.dll
1.1.2022.0
25-Feb-2006
07:57
1,843,712
x86
Sqlstpcustomdll.rll
1.1.2022.0
18-Feb-2006
06:49
12,288
Microsoft Data Access Components 2.8:
File Name Version Date Time Size CPU
dbnetlib.dll
2000.85.1062.0000
7-Mar-2006
14:27
73,728
x86
dbnmpntw.dll
2000.85.1062.0000
7-Mar-2006
14:27
28,672
x86
msadce.dll
2.80.1062.0000
7-Mar-2006
14:27
315,392
x86
msadco.dll
2.80.1062.0000
7-Mar-2006
14:27
135,168
x86
msadcs.dll
2.80.1062.0000
7-Mar-2006
14:27
49,152
x86
msadds.dll
2.80.1062.0000
7-Mar-2006
14:27
147,456
x86
msado15.dll
2.80.1062.0000
7-Mar-2006
14:27
507,904
x86
msadomd.dll
2.80.1062.0000
7-Mar-2006
14:27
163,840
x86
msadox.dll
2.80.1062.0000
7-Mar-2006
14:27
184,320
x86
msadrh15.dll
2.80.1062.0000
7-Mar-2006
14:27
53,248
x86
msdaora.dll
2.80.1062.0000
7-Mar-2006
14:27
225,280
x86
msdaprst.dll
2.80.1062.0000
7-Mar-2006
14:27
192,512
x86
msdart.dll
2.80.1062.0000
7-Mar-2006
14:27
147,456
x86
msdasql.dll
2.80.1062.0000
7-Mar-2006
14:27
303,104
x86
msorcl32.dll
2.575.1062.0000
7-Mar-2006
14:27
139,264
x86
odbc32.dll
3.525.1062.0000
7-Mar-2006
14:27
221,184
x86
odbcbcp.dll
2000.85.1062.0000
7-Mar-2006
14:27
24,576
x86
oledb32.dll
2.80.1062.0000
7-Mar-2006
14:27
442,368
x86
sqloledb.dll
2000.85.1062.0000
7-Mar-2006
14:27
503,808
x86
sqlsrv32.dll
2000.85.1062.0000
7-Mar-2006
14:27
401,408
x86
sqlxmlx.dll
2000.85.1062.0000
7-Mar-2006
14:27
208,896
x86
datasource.xml
7-Mar-2006
14:27
25,166
sqlse.rll
1.01.2022.0000
17-Feb-2006
15:02
45,056
x86
sqlstpcustomdll.dll
1.01.2022.0000
7-Mar-2006
14:27
1,843,712
x86
sqlstpcustomdll.rll
1.01.2022.0000
17-Feb-2006
15:02
12,288
x86
sprecovr.exe
6.02.0029.0000
17-Feb-2006
15:04
29,408
x86
spuninst.exe
6.02.0029.0000
17-Feb-2006
15:04
213,216
x86
spupdsvc.exe
6.02.0029.0000
17-Feb-2006
15:04
22,752
x86
Microsoft Data Access Components 2.8 Service Pack 1:
File Name Version Date Time Size CPU
Sprecovr.exe
6.2.29.0
17-Feb-2006
22:04
29,408
x86
Spupdsvc.exe
6.2.29.0
17-Feb-2006
22:04
22,752
x86
Msadco.dll
2.81.1124.0
22-Feb-2006
06:35
143,360
x86
Msado15.dll
2.81.1124.0
22-Feb-2006
06:35
524,288
x86
Msadomd.dll
2.81.1124.0
22-Feb-2006
06:35
180,224
x86
Msadox.dll
2.81.1124.0
22-Feb-2006
06:35
200,704
x86
Msdasql.dll
2.81.1124.0
22-Feb-2006
06:35
307,200
x86
Msjro.dll
2.81.1124.0
22-Feb-2006
06:35
102,400
x86
Sqloledb.dll
2000.85.1124.0
22-Feb-2006
06:35
520,192
x86
Datasource.xml
22-Feb-2006
06:35
22,450
Sqlse.rll
1.1.2022.0
17-Feb-2006
22:02
45,056
Sqlstpcustomdll.dll
1.1.2022.0
22-Feb-2006
06:36
1,843,712
x86
Sqlstpcustomdll.rll
1.1.2022.0
17-Feb-2006
22:02
12,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.
Click Start, and then click Search.
In the Search Results pane, click All files and folders under Search Companion.
In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
On the Version tab, determine the version of the file that is installed on your 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.
Microsoft Data Access Components 2.5 Service Pack 3:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\DataAccess\MDAC25\SP3\KB911562\Filelist
Microsoft Data Access Components 2.7 Service Pack 1:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\DataAccess\MDAC27\SP1\KB911562\Filelist
Microsoft Data Access Components 2.8:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\DataAccess\MDAC28\SP0\KB911562\Filelist
Microsoft Data Access Components 2.8 Service Pack 1:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\DataAccess\MDAC28\SP1\KB911562\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 911562 security update into the Windows installation source files.
Top of sectionTop of section
Top of sectionTop of section
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
•
Golan Yosef of Finjan's Malicious Code Research Center (MCRC) for working with Microsoft for the Microsoft Windows MDAC Vulnerability - CVE-2006-0003.
•
Stefano Meller and Mirko Gatto of Yarix for working with Microsoft for the Microsoft Windows MDAC Vulnerability - CVE-2006-0003.
Obtaining Other Security Updates:
Updates for other security issues are available at the following locations:
•
Security updates are available in the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch."
•
Updates for consumer platforms are available at the Microsoft Update Web site.
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:
•
The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.
•
Microsoft Software Update Services
•
Microsoft Windows Server Update Services
•
Microsoft Baseline Security Analyzer (MBSA)
•
Windows Update
•
Microsoft Update
•
Windows Update Catalog: For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166.
•
Office Update
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 Scanning 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 (April 11, 2006): Bulletin published.
Related
