Security Bulletin
Microsoft Security Bulletin MS11-002 - Critical
Vulnerabilities in Microsoft Data Access Components Could Allow Remote Code Execution (2451910)
Published: January 11, 2011
Version: 1.0
General Information
Executive Summary
This security update resolves two privately reported vulnerabilities in Microsoft Data Access Components. The vulnerabilities could allow remote code execution if a user views a specially crafted Web page. 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.
This security update is rated Critical for all supported editions of Windows XP, Windows Vista, and Windows 7, and Important for all supported editions of Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The security update addresses the vulnerabilities by ensuring that MDAC correctly validates string length and memory allocation. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
Recommendation. The majority of customers have automatic updating enabled and will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.
For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update immediately using update management software, or by checking for updates using the Microsoft Update service.
See also the section, Detection and Deployment Tools and Guidance, later in this bulletin.
Known Issues. None
Affected and Non-Affected Software
The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.
Affected Software
Windows Operating System and Components
Operating System | Component | Maximum Security Impact | Aggregate Severity Rating | Bulletins Replaced by this Update |
---|---|---|---|---|
Windows XP Service Pack 3 | Microsoft Data Access Components 2.8 Service Pack 1 (KB2419632) |
Remote Code Execution | Critical | None |
Windows XP Professional x64 Edition Service Pack 2 | Microsoft Data Access Components 2.8 Service Pack 2 (KB2419635) |
Remote Code Execution | Critical | None |
Windows Server 2003 Service Pack 2 | Microsoft Data Access Components 2.8 Service Pack 2 (KB2419635) |
Remote Code Execution | Important | None |
Windows Server 2003 x64 Edition Service Pack 2 | Microsoft Data Access Components 2.8 Service Pack 2 (KB2419635) |
Remote Code Execution | Important | None |
Windows Server 2003 with SP2 for Itanium-based Systems | Microsoft Data Access Components 2.8 Service Pack 2 (KB2419635) |
Remote Code Execution | Important | None |
Windows Vista Service Pack 1 and Windows Vista Service Pack 2 | Windows Data Access Components 6.0 (KB2419640) |
Remote Code Execution | Critical | None |
Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2 | Windows Data Access Components 6.0 (KB2419640) |
Remote Code Execution | Critical | None |
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2 | Windows Data Access Components 6.0* (KB2419640) |
Remote Code Execution | Important | None |
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2 | Windows Data Access Components 6.0* (KB2419640) |
Remote Code Execution | Important | None |
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 | Windows Data Access Components 6.0 (KB2419640) |
Remote Code Execution | Important | None |
Windows 7 for 32-bit Systems | Windows Data Access Components 6.0 (KB2419640) |
Remote Code Execution | Critical | None |
Windows 7 for x64-based Systems | Windows Data Access Components 6.0 (KB2419640) |
Remote Code Execution | Critical | None |
Windows Server 2008 R2 for x64-based Systems | Windows Data Access Components 6.0* (KB2419640) |
Remote Code Execution | Important | None |
Windows Server 2008 R2 for Itanium-based Systems | Windows Data Access Components 6.0 (KB2419640) |
Remote Code Execution | Important | None |
Affected Software | DSN Overflow Vulnerability - CVE-2011-0026 | ADO Record Memory Vulnerability - CVE-2011-0027 | Aggregate Severity Rating |
---|---|---|---|
Microsoft Data Access Components 2.8 Service Pack 1 on Windows XP Service Pack 3 | Important Remote Code Execution |
Critical Remote Code Execution |
Critical |
Microsoft Data Access Components 2.8 Service Pack 2 on Windows XP Professional x64 Edition Service Pack 2 | Important Remote Code Execution |
Critical Remote Code Execution |
Critical |
Microsoft Data Access Components 2.8 Service Pack 2 on Windows Server 2003 Service Pack 2 | Important Remote Code Execution |
Moderate Remote Code Execution |
Important |
Microsoft Data Access Components 2.8 Service Pack 2 on Windows Server 2003 x64 Edition Service Pack 2 | Important Remote Code Execution |
Moderate Remote Code Execution |
Important |
Microsoft Data Access Components 2.8 Service Pack 2 on Windows Server 2003 with SP2 for Itanium-based Systems | Important Remote Code Execution |
Moderate Remote Code Execution |
Important |
Windows Data Access Components 6.0 on Windows Vista Service Pack 1 and Windows Vista Service Pack 2 | Important Remote Code Execution |
Critical Remote Code Execution |
Critical |
Windows Data Access Components 6.0 on Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2 | Important Remote Code Execution |
Critical Remote Code Execution |
Critical |
Windows Data Access Components 6.0 on Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2* | Important Remote Code Execution |
Moderate Remote Code Execution |
Important |
Windows Data Access Components 6.0 on Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2* | Important Remote Code Execution |
Moderate Remote Code Execution |
Important |
Windows Data Access Components 6.0 on Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 | Important Remote Code Execution |
Moderate Remote Code Execution |
Important |
Windows Data Access Components 6.0 on Windows 7 for 32-bit Systems | Important Remote Code Execution |
Critical Remote Code Execution |
Critical |
Windows Data Access Components 6.0 on Windows 7 for x64-based Systems | Important Remote Code Execution |
Critical Remote Code Execution |
Critical |
Windows Data Access Components 6.0 on Windows Server 2008 R2 for x64-based Systems* | Important Remote Code Execution |
Moderate Remote Code Execution |
Important |
Windows Data Access Components 6.0 on Windows Server 2008 R2 for Itanium-based Systems | Important Remote Code Execution |
Moderate Remote Code Execution |
Important |
takeown /f "%ProgramFiles%\Common Files\System\ado\msado15.dll"
icacls "%ProgramFiles%\Common Files\System\ado\msado15.dll" /save %TEMP%\MSADO15_ACL64.TXT
icacls "%ProgramFiles%\Common Files\System\ado\msado15.dll" /deny everyone(F)
```
**Impact of workaround.** Disabling the ActiveX Data Objects (ADO) DLL will break MDAC functionality.
**How to undo the workaround:**
Run the following commands from a command prompt as an administrator:
For 32-bit editions of Windows XP and Windows Server 2003:
`cacls "%ProgramFiles%\Common Files\System\ado\msado15.dll" /E /R everyone`
For 64-bit editions of Windows XP and Windows Server 2003:
```
cacls "%ProgramFiles(86)%\Common Files\System\ado\msado15.dll" /E /R everyone
cacls "%ProgramFiles%\Common Files\System\ado\msado15.dll" /E /R everyone
```
For 32-bit editions of Windows Vista, Windows Server 2008, and Windows 7:
`icacls "%ProgramFiles(86)%\Common Files\System\ado\" /restore %TEMP%\MSADO15_ACL.TXT`
For 64-bit editions of Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2:
```
icacls "%ProgramFiles(86)%\Common Files\System\ado\" /restore %TEMP%\MSADO15_ACL.TXT
icacls "%ProgramFiles%\Common Files\System\ado\" /restore %TEMP%\MSADO15_ACL64.TXT
```
FAQ for ADO Record Memory Vulnerability - CVE-2011-0027
What is the scope of the vulnerability?
This is a remote code execution vulnerability. 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.
What causes the vulnerability?
MDAC does not correctly allocate memory when handling internal data structures.
What is Microsoft Data Access Components?
Microsoft Data Access Components (MDAC) is a collection of components that make it easy for programs to access databases and then to manipulate the data within them. Modern databases may take a variety of forms (for example, SQL Server databases, Microsoft Access databases, and XML files) and may be housed in a variety of locations (for example, on the local system or on a remote database server). MDAC provides a consolidated set of functions for working with different kinds of data sources in a consistent manner. Starting with Windows Vista, MDAC is referred to as Windows Data Access Components (WDAC).
ActiveX Data Objects (ADO), part of MDAC, is a language-neutral object model that exposes data raised by an underlying OLE DB Provider.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could gain the same user rights as a logged-on user. If the 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.
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 convince a user to view the Web site. The attacker could also take advantage of compromised Web sites and Web sites that accept or host user-provided content or advertisements. 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 convince users to visit the Web site, typically by getting them to click a link in an e-mail message or in an Instant Messenger message 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 be logged on and visiting 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 for Windows Server 2003, Windows Server 2008, or Windows Server 2008 R2. Does this mitigate this vulnerability?
Yes. By default, Internet Explorer on Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2 runs in a restricted mode that is known as Enhanced Security Configuration. Enhanced Security Configuration is a group of preconfigured settings in Internet Explorer that can reduce the likelihood of a user or administrator downloading and running specially crafted Web content on a server. This is a mitigating factor for Web sites that you have not added to the Internet Explorer Trusted sites zone.
What does the update do?
The update addresses this vulnerability by ensuring that MDAC correctly validates memory allocation.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through coordinated vulnerability disclosure.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.
Update Information
Detection and Deployment Tools and Guidance
Security Central
Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.
Security updates are available from Microsoft Update and Windows Update. Security updates are also available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update."
Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, "MS07-036"), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ.
Detection and Deployment Guidance
Microsoft provides detection and deployment guidance for security updates. This guidance contains recommendations and information that can help IT professionals understand how to use various tools for detection and deployment of security updates. For more information, see Microsoft Knowledge Base Article 961747.
Microsoft Baseline Security Analyzer
Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA, visit Microsoft Baseline Security Analyzer.
The following table provides the MBSA detection summary for this security update.
Software | MBSA |
---|---|
Windows XP Service Pack 3 | Yes |
Windows XP Professional x64 Edition Service Pack 2 | Yes |
Windows Server 2003 Service Pack 2 | Yes |
Windows Server 2003 x64 Edition Service Pack 2 | Yes |
Windows Server 2003 with SP2 for Itanium-based Systems | Yes |
Windows Vista Service Pack 1 and Windows Vista Service Pack 2 | Yes |
Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2 | Yes |
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2 | Yes |
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2 | Yes |
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 | Yes |
Windows 7 for 32-bit Systems | Yes |
Windows 7 for x64-based Systems | Yes |
Windows Server 2008 R2 for x64-based Systems | Yes |
Windows Server 2008 R2 for Itanium-based Systems | Yes |
Note For customers using legacy software not supported by the latest release of MBSA, Microsoft Update, and Windows Server Update Services, please visit Microsoft Baseline Security Analyzer and reference the Legacy Product Support section on how to create comprehensive security update detection with legacy tools.
Windows Server Update Services
Windows Server Update Services (WSUS) enables information technology administrators to deploy the latest Microsoft product updates to computers that are running the Windows operating system. For more information about how to deploy security updates using Windows Server Update Services, see the TechNet article, Windows Server Update Services.
Systems Management Server
The following table provides the SMS detection and deployment summary for this security update.
Software | SMS 2.0 | SMS 2003 with SUIT | SMS 2003 with ITMU | Configuration Manager 2007 |
---|---|---|---|---|
Windows XP Service Pack 3 | Yes | Yes | Yes | Yes |
Windows XP Professional x64 Edition Service Pack 2 | No | No | Yes | Yes |
Windows Server 2003 Service Pack 2 | Yes | Yes | Yes | Yes |
Windows Server 2003 x64 Edition Service Pack 2 | No | No | Yes | Yes |
Windows Server 2003 with SP2 for Itanium-based Systems | No | No | Yes | Yes |
Windows Vista Service Pack 1 and Windows Vista Service Pack 2 | No | No | Yes | Yes |
Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2 | No | No | Yes | Yes |
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2 | No | No | Yes | Yes |
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2 | No | No | Yes | Yes |
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 | No | No | Yes | Yes |
Windows 7 for 32-bit Systems | No | No | Yes | Yes |
Windows 7 for x64-based Systems | No | No | Yes | Yes |
Windows Server 2008 R2 for x64-based Systems | No | No | Yes | Yes |
Windows Server 2008 R2 for Itanium-based Systems | No | No | Yes | Yes |
For SMS 2.0 and SMS 2003, the Security Update Inventory Tool (SUIT) can be used by SMS to detect security updates. See also Downloads for Systems Management Server 2.0.
For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates. For more information about SMS scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.
System Center Configuration Manager 2007 uses WSUS 3.0 for detection of updates. For more information about Configuration Manager 2007 Software Update Management, visit System Center Configuration Manager 2007.
For more information about SMS, visit the SMS Web site.
For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.
Update Compatibility Evaluator and Application Compatibility Toolkit
Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit.
The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.
Security Update Deployment
Affected Software
For information about the specific security update for your affected software, click the appropriate link:
Windows XP (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
Deployment | |
Installing without user intervention | For Microsoft Data Access Components 2.8 Service Pack 1 on Windows XP Service Pack 3: WindowsXP-KB2419632-x86-enu.exe /quiet |
For Microsoft Data Access Components 2.8 Service Pack 2 on Windows XP Professional x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-KB2419635-x64-enu.exe /quiet |
|
Installing without restarting | For Microsoft Data Access Components 2.8 Service Pack 1 on Windows XP Service Pack 3: WindowsXP-KB2419632-x86-enu.exe /norestart |
For Microsoft Data Access Components 2.8 Service Pack 2 on Windows XP Professional x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-KB2419635-x64-enu.exe /norestart |
|
Update log file | For Microsoft Data Access Components 2.8 Service Pack 1 on Windows XP Service Pack 3: KB2419632.log |
For Microsoft Data Access Components 2.8 Service Pack 2 on Windows XP Professional x64 Edition Service Pack 2: KB2419635.log |
|
Further information | See the subsection, Detection and Deployment Tools and Guidance |
Restart Requirement | |
Restart required? | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. |
HotPatching | Not applicable |
Removal Information | For Microsoft Data Access Components 2.8 Service Pack 1 on Windows XP Service Pack 3: Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB2419632$\Spuninst folder |
For Microsoft Data Access Components 2.8 Service Pack 2 on Windows XP Professional x64 Edition Service Pack 2: Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB2419635$\Spuninst folder |
|
File Information | For Microsoft Data Access Components 2.8 Service Pack 1 on Windows XP Service Pack 3: See Microsoft Knowledge Base Article 2419632 |
For Microsoft Data Access Components 2.8 Service Pack 2 on Windows XP Professional x64 Edition Service Pack 2: See Microsoft Knowledge Base Article 2419635 |
|
Registry Key Verification | For Microsoft Data Access Components 2.8 Service Pack 1 on Windows XP Service Pack 3: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB2419632\Filelist |
For Microsoft Data Access Components 2.8 Service Pack 2 on Windows XP Professional x64 Edition Service Pack 2: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB2419635\Filelist |
Note For supported versions of Windows XP Professional x64 Edition, this security update is the same as supported versions of the Windows Server 2003 x64 Edition security update.
Deployment Information
Installing the Update
When you install this security update, the installer checks whether 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 installer, see Microsoft Knowledge Base Article 832475.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
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** | Displays 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. |
Removing the Update
This security update supports the following setup 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** | Displays 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. |
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
- 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 edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. - On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.
These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.
Windows Server 2003 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
Deployment | |
Installing without user intervention | For Microsoft Data Access Components 2.8 Service Pack 2 on all supported 32-bit editions of Windows Server 2003: WindowsServer2003-KB2419635-x86-enu.exe /quiet |
For Microsoft Data Access Components 2.8 Service Pack 2 on all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB2419635-x64-enu.exe /quiet |
|
For Microsoft Data Access Components 2.8 Service Pack 2 on all supported Itanium-based editions of Windows Server 2003: WindowsServer2003-KB2419635-ia64-enu.exe /quiet |
|
Installing without restarting | For Microsoft Data Access Components 2.8 Service Pack 2 on all supported 32-bit editions of Windows Server 2003: WindowsServer2003-KB2419635-x86-enu.exe /norestart |
For Microsoft Data Access Components 2.8 Service Pack 2 on all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB2419635-x64-enu.exe /norestart |
|
For Microsoft Data Access Components 2.8 Service Pack 2 on all supported Itanium-based editions of Windows Server 2003: WindowsServer2003-KB2419635-ia64-enu.exe /norestart |
|
Update log file | KB2419635.log |
Further information | See the subsection, Detection and Deployment Tools and Guidance |
Restart Requirement | |
Restart required? | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. |
HotPatching | This security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341. |
Removal Information | Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB2419635$\Spuninst folder |
File Information | See Microsoft Knowledge Base Article 2419635 |
Registry Key Verification | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2419635\Filelist |
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** | Displays 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. |
Removing the Update
This security update supports the following setup 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** | Displays 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. |
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
- 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 edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. - On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.
These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.
Windows Vista (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
Deployment | |
Installing without user intervention | For Windows Data Access Components 6.0 on all supported 32-bit editions of Windows Vista: Windows6.0-KB2419640-x86.msu /quiet |
For Windows Data Access Components 6.0 on all supported x64-based editions of Windows Vista: Windows6.0-KB2419640-x64.msu /quiet |
|
Installing without restarting | For Windows Data Access Components 6.0 on all supported 32-bit editions of Windows Vista: Windows6.0-KB2419640-x86.msu /quiet /norestart |
For Windows Data Access Components 6.0 on all supported x64-based editions of Windows Vista: Windows6.0-KB2419640-x64.msu /quiet /norestart |
|
Further information | See the subsection, Detection and Deployment Tools and Guidance |
Restart Requirement | |
Restart required? | 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. |
HotPatching | Not applicable. |
Removal Information | WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates. |
File Information | See Microsoft Knowledge Base Article 2419640 |
Registry Key Verification | Note A registry key does not exist to validate the presence of this update. |
Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
Deployment | |
Installing without user intervention | For Windows Data Access Components 6.0 on all supported 32-bit editions of Windows Server 2008: Windows6.0-KB2419640-x86.msu /quiet |
For Windows Data Access Components 6.0 on all supported x64-based editions of Windows Server 2008: Windows6.0-KB2419640-x64.msu /quiet |
|
For Windows Data Access Components 6.0 on all supported Itanium-based editions of Windows Server 2008: Windows6.0-KB2419640-ia64.msu /quiet |
|
Installing without restarting | For Windows Data Access Components 6.0 on all supported 32-bit editions of Windows Server 2008: Windows6.0-KB2419640-x86.msu /quiet /norestart |
For Windows Data Access Components 6.0 on all supported x64-based editions of Windows Server 2008: Windows6.0-KB2419640-x64.msu /quiet /norestart |
|
For Windows Data Access Components 6.0 on all supported Itanium-based editions of Windows Server 2008: Windows6.0-KB2419640-ia64.msu /quiet /norestart |
|
Further information | See the subsection, Detection and Deployment Tools and Guidance |
Restart Requirement | |
Restart required? | 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. |
HotPatching | Not applicable. |
Removal Information | WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates. |
File Information | See Microsoft Knowledge Base Article 2419640 |
Registry Key Verification | Note A registry key does not exist to validate the presence of this update. |
Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
Deployment | |
Installing without user intervention | For Windows Data Access Components 6.0 on all supported 32-bit editions of Windows 7: Windows6.1-KB2419640-x86.msu /quiet |
For Windows Data Access Components 6.0 on all supported x64-based editions of Windows 7: Windows6.1-KB2419640-x64.msu /quiet |
|
Installing without restarting | For Windows Data Access Components 6.0 on all supported 32-bit editions of Windows 7: Windows6.1-KB2419640-x86.msu /quiet /norestart |
For Windows Data Access Components 6.0 on all supported x64-based editions of Windows 7: Windows6.1-KB2419640-x64.msu /quiet /norestart |
|
Further information | See the subsection, Detection and Deployment Tools and Guidance |
Restart Requirement | |
Restart required? | 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. |
HotPatching | Not applicable. |
Removal Information | To uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, and then under Windows Update, click View installed updates and select from the list of updates. |
File Information | See Microsoft Knowledge Base Article 2419640 |
Registry Key Verification | Note A registry key does not exist to validate the presence of this update. |
Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
Deployment | |
Installing without user intervention | For Windows Data Access Components 6.0 on all supported x64-based editions of Windows Server 2008 R2: Windows6.1-KB2419640-x64.msu /quiet |
For Windows Data Access Components 6.0 on all supported Itanium-based editions of Windows Server 2008 R2: Windows6.1-KB2419640-ia64.msu /quiet |
|
Installing without restarting | For Windows Data Access Components 6.0 on all supported x64-based editions of Windows Server 2008 R2: Windows6.1-KB2419640-x64.msu /quiet /norestart |
For Windows Data Access Components 6.0 on all supported Itanium-based editions of Windows Server 2008 R2: Windows6.1-KB2419640-ia64.msu /quiet /norestart |
|
Further information | See the subsection, Detection and Deployment Tools and Guidance |
Restart Requirement | |
Restart required? | 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. |
HotPatching | Not applicable. |
Removal Information | To uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, and then under Windows Update, click View installed updates and select from the list of updates. |
File Information | See Microsoft Knowledge Base Article 2419640 |
Registry Key Verification | Note A registry key does not exist to validate the presence of this update. |