Security Bulletin
Microsoft Security Bulletin MS08-028 - Critical
Vulnerability in Microsoft Jet Database Engine Could Allow Remote Code Execution (950749)
Published: May 13, 2008 | Updated: July 16, 2008
Version: 1.3
General Information
Executive Summary
This security update resolves a security vulnerability in the Microsoft Jet Database Engine (Jet) in Windows. 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.
This security update is rated Critical for the Microsoft Jet 4.0 Database Engine. For more information, see the subsection, Affected and Non-Affected Software, in this section.
This security update addresses the vulnerability by modifying the way that the Microsoft Jet Database Engine parses data within a database. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
This security update also addresses the vulnerability first described in Microsoft Security Advisory 950627. In addition to installing this update, we recommend that customers with Microsoft Word also install the updates provided in Microsoft Security Bulletin MS08-026: Vulnerabilities in Microsoft Word Could Allow Remote Code Execution (951207) for the most up-to-date protection of the attack vector for these types of attacks.
Recommendation. Microsoft recommends that customers apply the update immediately.
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
| Operating System | Component | Maximum Security Impact | Aggregate Severity Rating | Bulletins Replaced by this Update |
|---|---|---|---|---|
| Microsoft Windows 2000 Service Pack 4 | Microsoft Jet 4.0 Database Engine* | Remote Code Execution | Critical | MS04-014 |
| Windows XP Service Pack 2 | Microsoft Jet 4.0 Database Engine* | Remote Code Execution | Critical | None |
| Windows XP Professional x64 Edition | Microsoft Jet 4.0 Database Engine* | Remote Code Execution | Critical | None |
| Windows Server 2003 Service Pack 1 | Microsoft Jet 4.0 Database Engine* | Remote Code Execution | Critical | None |
| Windows Server 2003 x64 Edition | Microsoft Jet 4.0 Database Engine* | Remote Code Execution | Critical | None |
| Windows Server 2003 with SP1 for Itanium-based Systems | Microsoft Jet 4.0 Database Engine* | Remote Code Execution | Critical | None |
* These operating systems are delivered with the affected version of Jet, specifically the file msjet40.dll, with a version lower than 4.0.9505.0. See also the FAQ subsection for the specific vulnerability entry under the next section, Vulnerability Information.
Non-Affected Software
| Operating System | Component |
|---|---|
| Windows XP Professional x64 Edition Service Pack 2 | Microsoft Jet 4.0 Database Engine** |
| Windows XP Service Pack 3 | Microsoft Jet 4.0 Database Engine** |
| Windows Server 2003 Service Pack 2 | Microsoft Jet 4.0 Database Engine** |
| Windows Server 2003 x64 Edition Service Pack 2 | Microsoft Jet 4.0 Database Engine** |
| Windows Server 2003 with SP2 for Itanium-based Systems | Microsoft Jet 4.0 Database Engine** |
| Windows Vista and Windows Vista Service Pack 1 | Microsoft Jet 4.0 Database Engine** |
| Windows Vista for x64-based Systems and Windows Vista Service Pack 1 for x64-based Systems | Microsoft Jet 4.0 Database Engine** |
| Windows Server 2008 for 32-bit Systems | Microsoft Jet 4.0 Database Engine** |
| Windows Server 2008 for x64-based Systems | Microsoft Jet 4.0 Database Engine** |
| Windows Server 2008 for Itanium-based Systems | Microsoft Jet 4.0 Database Engine** |
** These operating systems are delivered with the non-affected version of Jet, specifically the file msjet40.dll, with a version equal to or higher than 4.0.9505.0. See also the FAQ subsection for the specific vulnerability entry under the next section, Vulnerability Information.
Frequently Asked Questions (FAQ) Related to This Security Update
CVE-2005-0944 also describes a vulnerability in Microsoft Jet Engine. How does CVE-2005-0944 relate to this update?
The vulnerability referenced by CVE-2005-0944 has also been addressed by this update. The vulnerability details for CVE-2005-0944, including affected and non-affected software, mitigating factors, and workarounds remain the same as for CVE-2007-6026. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2005-0944.
Why is this update rated Critical?
While .mdb is on the unsafe file type list, there are attack scenarios that would bypass the mitigations provided for unsafe file-types. Specifically, customers with Microsoft Office could be at risk to e-mail or direct download attack scenarios. For example, an attacker could exploit the vulnerability by sending a Word file with a specially crafted .mdb file embedded in it to the user and convincing the user to open the document or view the e-mail containing the specially crafted file. In the case of Outlook 2003 and Outlook 2007, the attack could be executed by viewing the document in HTML in the Outlook 2003 or Outlook 2007 preview pane. We recommend these customers apply this update immediately.
Does this update protect against attacks via other applications?
Yes. There are applications that can be installed that can be used as an attack vector for this vulnerability. For example, a Jet database file can be opened from a Word document, from e-mail, or by visiting a malicious website. Applying this update will block those attacks. However, it is recommended that customers also apply the updates provided in Microsoft Security Bulletin MS08-026: Vulnerabilities in Microsoft Word Could Allow Remote Code Execution (951207) to fully block newly discovered attack vectors.
Are applications and services using the Extensible Storage Engine (ESE) formerly known as JET Blue vulnerable?
No. This vulnerability applies only to the Microsoft Jet 4.0 Database Engine. Applications and services using the Extensible Storage Engine are not affected.
I am using an older release of the software discussed in this security bulletin. What should I do?
The affected software listed in this bulletin have been tested to determine which releases are affected. Other releases are past their support life cycle. To determine the support life cycle for your software release, visit Microsoft Support Lifecycle.
It should be a priority for customers who have older releases of the software to migrate to supported releases to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit Microsoft Support Lifecycle. For more information about the extended security update support period for these software versions or editions, visit Microsoft Product Support Services.
Customers who require custom support for older releases must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit Microsoft Worldwide Information, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ.
Vulnerability Information
Severity Ratings and Vulnerability Identifiers
| Affected Software | Microsoft Jet Engine MDB File Parsing Stack Overflow Vulnerability - CVE-2007-6026 | Aggregate Severity Rating |
|---|---|---|
| Microsoft Jet 4.0 Database Engine | Critical\ Remote Code Execution | Critical |
Microsoft Jet Engine MDB File Parsing Stack Overflow Vulnerability - CVE-2007-6026
A buffer overrun vulnerability exists in the Microsoft Jet Database Engine (Jet) that could allow remote code execution on an affected system. An attacker could exploit the vulnerability by creating a specially crafted database query and sending it through an application that is using Jet on an affected system. 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.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2007-6026.
Mitigating Factors for Microsoft Jet Engine MDB File Parsing Stack Overflow Vulnerability - CVE-2007-6026
Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:
- An attacker 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 affected than users who operate with administrative user rights.
- In a Web-based attack scenario, an attacker would have to host a Web site that contains a specially crafted Word file that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's site.
- Systems that use Microsoft Outlook 2003 and 2007 as their e-mail client can mitigate the HTML email vector for Outlook 2007 by configuring mail to be read in plain text only.
- Systems running all supported editions of Windows XP Service Pack 3, Windows Server 2003 Service Pack 2, Windows Vista, and Windows Server 2008 are not affected by this vulnerability.
Workarounds for Microsoft Jet Engine MDB File Parsing Stack Overflow Vulnerability - CVE-2007-6026
Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:
Restrict the Microsoft Jet Database Engine from running for any application
To implement the workaround, enter the following command at a command prompt:echo y| cacls "%SystemRoot%\system32\msjet40.dll" /E /P everyone:NImpact of workaround. Any application requiring the use of the Microsoft Jet Database Engine to make data access calls will not function.
How to undo the workaround. Enter the following command at a command prompt
echo y| cacls "%SystemRoot%\system32\msjet40.dll" /E /R everyoneUse group policy to restrict the Microsoft Jet Database Engine from running for any application
To implement the workaround, perform the following steps:Create the following script, named JetCacls.cmd for illustration:
@echo off
if exist %systemdrive%\Cacls.log goto end
cacls "%SystemRoot%\system32\msjet40.dll" /E /P everyone:N > nul 2>&1
echo %date% %time%: Msjet Cacls updated > %systemdrive%\Cacls.log
:end
exitCopy JetCacls.cmd to the Netlogon shared folder, or another shared folder on the domain controller from which JetCacls.cmd would run.
Set up JetCacls.cmd. In the Active Directory Users and Computers MMC snap-in, right-click the domain name, and then click Properties.
Click the Group Policy tab.
Click New to create a new Group Policy object (GPO), and enter JetCacls for the name of the policy.
Click the new policy, and then click Edit.
Expand Windows Settings for Computer Configuration, and then click Scripts.
Double-click Logon, and then click Add. The Add a Script dialog box appears.
Type \\servername\sharename\JetCacls.cmd in the Script Name box.
Click OK, and then click Apply.
Then restart the client computers that are members of this domain.
Impact of workaround. Any application that requires the use of the Microsoft Jet Database Engine to make data access calls will not function. This restriction only applies to applications that are running on client computers in the domain.
Block MDB files from being processed through your mail infrastructure
Note All Jet database files should be treated as unsafe file types for common users and Microsoft recommends that database files transferred via e-mail be treated as suspicious.To implement this workaround, your mail environment must support the ability to search for attachments containing a specific file structure (not just the file extension) within an e-mail message and then perform actions on the attachment such as delete, quarantine, notify, and report the detected file.
To detect Jet files that have possibly been renamed to another file type, search for files with any of the following 15-byte signatures at location 0x4 (no quotes):
"Jet System DB " "Standard Jet DB" "Temp Jet DB "For configurations specific to Microsoft Exchange customers using Forefront (formerly Antigen) technologies, please see Microsoft Forefront Server Security: File Filtering for more information.
This information has been shared with members of Microsoft Security Response Alliance. To utilize the MSRA tools to detect MDB files, please contact the providers as listed on the MSRA home page.
Impact of Workaround. Files detected by this configuration will be blocked from processing through an organization’s e-mail system.
Configure Outlook 2007 to read mail in plain text.
Do not open or save Jet or Microsoft Word files that you receive from untrusted sources or that you receive unexpectedly from trusted sources. This vulnerability could be exploited when a user opens a specially crafted file.
FAQ for Microsoft Jet Engine MDB File Parsing Stack Overflow Vulnerability - CVE-2007-6026
What is the scope of the vulnerability?
This is a remote code execution vulnerability. A remote, anonymous attacker who successfully exploited this vulnerability could run arbitrary code in the context of the local user.
What causes the vulnerability?
The Microsoft Jet Database Engine (Jet) does not perform sufficient validation of a data structure. An attacker could exploit the vulnerability by creating a specially crafted database query and sending it through an application that is using Jet on an affected system.
What is the Microsoft Jet Database Engine (Jet)?
The Microsoft Jet Database Engine provides data access to applications such as Microsoft Access, Microsoft Visual Basic, and many third party applications. Jet can also be used by Internet applications that require database functionality.
Aren’t .mdb files on the unsafe file type list? If so, why is this a Critical vulnerability?
While .mdb is on the unsafe file type list, a new attack vector has been discovered where a Jet database file can be opened from a Word document. This update will block current attacks as well as provide additional fixes for the Jet Database Engine. However, it is recommended that customers also apply the updates provided in Microsoft Security Bulletin MS08-026: Vulnerabilities in Microsoft Word Could Allow Remote Code Execution (951207) to block the newly discovered attack vector.
Should .mdb files still be considered unsafe?
Yes. While this update blocks active attacks, .mdb database files perform unsafe functions by design. Customers should still treat these files with caution. Furthermore, supported Microsoft e-mail applications will continue to block .mdb files from being opened.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user. If a user is logged on with administrative user rights, an attacker could take complete control of the 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.
How could an attacker exploit the vulnerability?
An attacker could exploit this vulnerability by convincing a user to open a specially crafted database file using Jet. 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 affected than users who operate with administrative user rights.
In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a Word file with a specially crafted .mdb file embedded in it to the user and by convincing the user to open the document or view the email containing the specially crafted file. Or in the case of Outlook 2003 and Outlook 2007, the attack could be executed by viewing the document in HTML in the Outlook 2003 or Outlook 2007 preview pane.
In a Web-based attack scenario, an attacker would have to host a Web site that contains a Jet file or a Word file with a specially crafted Jet file embedded in it to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes them to the attacker's site.
Is there anything that helps mitigate the risk of an HTML email attack?
Systems using Microsoft Outlook as their e-mail client can mitigate the HTML email vector for Outlook 2003 and Outlook 2007 by configuring mail to be read in plain text only.
What systems are primarily at risk from the vulnerability?
Systems where a vulnerable version of the Microsoft Jet 4.0 Database Engine is installed on supported editions of Microsoft Windows 2000, Windows XP Service Pack 2, and Windows Server 2003 Service Pack 1 are primarily at risk. These operating systems, also listed in the Affected Software table in the General Information section, are delivered with the vulnerable version of Jet. Therefore, you may review the next FAQ on how to determine the vulnerable version of Jet on your system.
How do I know if I have a vulnerable version of Jet?
If the version of Msjet40.dll is lower than 4.0.9505.0, you have a vulnerable version of Jet on your system. Version 4.0.9505.0 and all higher versions of Msjet40.dll are not vulnerable to this buffer overrun.
What does the update do?
The update removes the vulnerability by improving the validation of data structures within Jet.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. This vulnerability has been publicly disclosed and has been commonly referred to as “Microsoft Jet Engine MDB File Parsing Stack Overflow Vulnerability” and assigned Common Vulnerability and Exposure number CVE 2007-6026.
Does this security update address the issue identified in Microsoft Security Advisory 950627?
Yes. The release of this security update addresses the security issue in Microsoft Security Advisory 950627 identified with CVE 2008-1092. After researching the issue, Microsoft has identified that it is the same issue as CVE-2007-6026 and as a result has been reclassified for this security bulletin.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
Yes. When the security bulletin was released, Microsoft had received information that this vulnerability was being exploited.
Does applying this security update help protect customers from the code, published publicly, that attempts to exploit this vulnerability?
Yes. This security update addresses the vulnerability that is currently being exploited. The vulnerability that has been addressed has been assigned the Common Vulnerability and Exposure number CVE-2007-6026.
Update Information
Detection and Deployment Tools and Guidance
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, Windows Update, and Office 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 has provided detection and deployment guidance for this month’s security updates. This guidance will also help IT professionals understand how they can use various tools to help deploy the security update, such as Windows Update, Microsoft Update, Office Update, the Microsoft Baseline Security Analyzer (MBSA), the Office Detection Tool, Microsoft Systems Management Server (SMS), and the Extended Security Update Inventory Tool. For more information, see Microsoft Knowledge Base Article 910723.
Microsoft Baseline Security Analyzer
Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA, visit Microsoft Baseline Security Analyzer.
The following table provides the MBSA detection summary for this security update.
| Software | MBSA 2.1 |
|---|---|
| Microsoft Windows 2000 Service Pack 4 | Yes |
| Windows XP Service Pack 2 | Yes |
| Windows XP Professional x64 Edition | Yes |
| Windows Server 2003 Service Pack 1 | Yes |
| Windows Server 2003 x64 Edition | Yes |
| Windows Server 2003 with SP1 for Itanium-based Systems | Yes |
For more information about MBSA 2.1, see MBSA 2.1 Frequently Asked Questions.
Windows Server Update Services
By using Windows Server Update Services (WSUS), administrators can deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 to Windows 2000 and later operating systems. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site.
Systems Management Server
The following table provides the SMS detection and deployment summary for this security update.
| Software | SMS 2.0 | SMS 2003 with SUSFP | SMS 2003 with ITMU | SCCM 2007 |
|---|---|---|---|---|
| Microsoft Windows 2000 Service Pack 4 | Yes | Yes | Yes | Yes |
| Windows XP Service Pack 2 | Yes | Yes | Yes | Yes |
| Windows XP Professional x64 Edition | No | No | Yes | Yes |
| Windows Server 2003 Service Pack 1 | Yes | Yes | Yes | Yes |
| Windows Server 2003 x64 Edition | No | No | Yes | Yes |
| Windows Server 2003 with SP1 for Itanium-based Systems | No | No | Yes | Yes |
For SMS 2.0 and SMS 2003, the SMS SUS Feature Pack (SUSFP), which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. See also Downloads for Systems Management Server 2.0.
For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications. For more information about the Office Inventory Tool and other scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.
System Center Configuration Manager (SCCM) 2007 uses WSUS 3.0 for detection of updates. For more information about SCCM 2007 Software Update Management, visit System Center Configuration Manager 2007.
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.
Security Update Deployment
Affected Software
For information about the specific security update for your affected software, click the appropriate link:
Windows 2000 (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 may be included in a future update rollup |
|---|---|
| Deployment | |
| Installing without user intervention | Microsoft Windows 2000 Service Pack 4:\ Windows2000-kb950749-x86-enu /quiet |
| Installing without restarting | Microsoft Windows 2000 Service Pack 4:\ Windows2000-kb950749-x86-enu /norestart |
| Update log file | Microsoft Windows 2000 Service Pack 4:\ kb950749.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 | Microsoft Windows 2000 Service Pack 4:\ Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%$NTUninstallKB950749$\Spuninst folder |
| File Information | See Microsoft Knowledge Base Article 950749. |
| Registry Key Verification | Microsoft Windows Service Pack 4: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB950749\Filelist |
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, 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.
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. |
| /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.
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. |
Verifying That the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
File Version Verification
Because there are several 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 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 | Windows XP Service Pack 2:\ Windowsxp-kb950749-x86-enu /quiet |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:\ WindowsServer2003.WindowsXP-kb950749-x64-enu /quiet | |
| Installing without restarting | Windows XP Service Pack 2:\ Windowsxp-kb950749-x86-enu /norestart |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:\ WindowsServer2003.WindowsXP-kb950749-x64-enu /norestart | |
| Update log file | KB950749.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 | Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%$NTUninstallKB950749$\Spuninst folder |
| File Information | See Microsoft Knowledge Base Article 950749. |
| Registry Key Verification | For all supported 32-bit editions of Windows XP:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB950749\Filelist |
| For all supported x64-based editions of Windows XP:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB950749\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, 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.
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. |
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.
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. |
Verifying That the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
File Version Verification
Because there are several 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 Windows Server 2003 Service Pack 1:\ Windowsserver2003-kb950749-x86-enu /quiet |
| For Windows Server 2003 x64 Edition:\ Windowsserver2003.WindowsXP-KB950749-x64-enu /quiet | |
| For Windows Server 2003 with SP1 for Itanium-based Systems:\ Windowsserver2003-KB950749-ia64-enu /quiet | |
| Installing without restarting | For Windows Server 2003 Service Pack 1:\ Windowsserver2003-kb950749-x86-enu /norestart |
| For Windows Server 2003 x64 Edition:\ Windowsserver2003.WindowsXP-KB950749-x64-enu /norestart | |
| For Windows Server 2003 with SP1 for Itanium-based Systems:\ Windowsserver2003-KB950749-ia64-enu /norestart | |
| Update log file | KB950749.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%$NTUninstallKB950749$\Spuninst folder |
| File Information | See Microsoft Knowledge Base Article 950749. |
| Registry Key Verification | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP2\KB950749\Filelist |
Deployment Information
Installing the Update
When you install this security update, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
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, 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.
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. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Removing the Update
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. |
Verifying that the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
File Version Verification
Because there are several 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.
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
- CERT/CC for reporting the issue - CVE-2007-6026
- ISC/SANS for reporting the issue - CVE-2007-6026
- Aaron Portnoy of TippingPoint DVLabs for reporting the issue - CVE-2007-6026
Support
- Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.
- International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.
Disclaimer
The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
Revisions
- V1.0 (May 13, 2008): Bulletin published.
- V1.1 (May 28, 2008): Added entry to Update FAQ to clarify that CVE-2005-0944 was also addressed by this update.
- V1.2 (June 4, 2008): Added a link to Microsoft Knowledge Base Article 950749 under Known Issues in the Executive Summary.
- V1.3 (July 16, 2008): Removed link to Microsoft Knowledge Base Article 950749 under Known Issues in the Executive Summary.
Built at 2014-04-18T13:49:36Z-07:00