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

Microsoft Security Bulletin MS07-022 - Important

Vulnerability in Windows Kernel Could Allow Elevation of Privilege (931784)

Published: April 10, 2007 | Updated: June 26, 2007

Version: 2.0

Summary

Who Should Read this Document: Customers who use Microsoft Windows

Impact of Vulnerability: Elevation of Privilege

Maximum Severity Rating: Important

Recommendation: Customers should apply the update at the earliest opportunity

Security Update Replacement: This bulletin replaces a prior security update. See the Frequently Asked Questions (FAQ) section of this bulletin for details.

Tested Software and Security Update Download Locations:

Affected Software:

Non-Affected Software:

  • Microsoft Windows XP Professional x64 Edition and Microsoft Windows XP Professional x64 Edition Service Pack 2
  • Microsoft Windows Server 2003 x64 Edition and Microsoft Windows Server 2003 x64 Edition Service Pack 2
  • Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with SP1 and SP2 for Itanium-based Systems
  • Windows Vista
  • Windows Vista x64 Edition

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

General Information

Executive Summary:

This update resolves a newly discovered, privately reported vulnerability. The vulnerability is documented in its own subsection in the Vulnerability Details section of this bulletin.

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.

We recommend that customers apply the update at the earliest opportunity.

Severity Ratings and Vulnerability Identifiers:

Vulnerability IdentifiersImpact of VulnerabilityMicrosoft Windows 2000 Service Pack 4Microsoft Windows XP Service Pack 2Microsoft Windows Server 2003Microsoft Windows Server 2003 Service Pack 1Microsoft Windows Server 2003 Service Pack 2
Kernel Local Elevation of Privilege Vulnerability - CVE-2007-1206Elevation of PrivilegeImportantImportantImportantImportantImportant

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

Why did Microsoft reissue this bulletin on June 26 2007?
Microsoft updated this bulletin to advise customers with Windows 2000 Service Pack 4 installed on NEC 98 systems that a revised version of the security update is available. These systems may encounter problems when trying to connect to Windows Update due to an incorrect build version of the security update for the NEC 98 systems. The original security update successfully addressed the vulnerabilities described in this security bulletin.

Microsoft recommends that NEC 98 customers with Windows 2000 Service Pack 4 download the revised security update from the Microsoft Download Center web site to ensure that Windows Update offers future updates correctly. NEC 98 customers running Windows 2000 Service pack 4 may also uninstall this security update in order to receive the revised security update from Windows Update automatically.

For more information on this issue see Microsoft Knowledge Base Article 931784. Microsoft Knowledge Base Article 931784documents the currently known issues that customers may experience when they install this revised security update.

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

Bulletin IDMicrosoft Windows 2000 Service Pack 4Microsoft Windows XP Service Pack 2Microsoft Windows Server 2003Microsoft Windows Server 2003 Service Pack 1Microsoft Windows Server 2003 Service Pack 2
MS06-049ReplacedNot ApplicableNot ApplicableNot ApplicableNot Applicable

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

ProductMBSA 1.2.1MBSA 2.0.1
Microsoft Windows 2000 Service Pack 4YesYes
Microsoft Windows XP Service Pack 2YesYes
Microsoft Windows Server 2003, Microsoft Windows Server 2003 Service Pack 1, and Microsoft Windows Server 2003 Service Pack 2YesYes

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

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

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

ProductSMS 2.0SMS 2003
Microsoft Windows 2000 Service Pack 4YesYes
Microsoft Windows XP Service Pack 2YesYes
Microsoft Windows Server 2003, Microsoft Windows Server 2003 Service Pack 1, and Microsoft Windows Server 2003 Service Pack 2YesYes

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

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

For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, visit the following Microsoft Web site. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

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

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

I am using an older version of the software discussed in this security bulletin; what should I do? 
The affected software listed in this bulletin has been tested to determine whether the versions are affected. Other versions are past their support life cycle. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.

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

Customers who require custom support for older software must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ.

Kernel Local Elevation of Privilege Vulnerability - CVE-2007-1206:

A privilege elevation vulnerability exists in Windows Kernel because of incorrect permissions on a mapped memory segment. An attacker who successfully exploited this vulnerability could take complete control of an affected system.

Mitigating Factors for Kernel Local Elevation of Privilege Vulnerability - CVE-2007-1206:

An attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability. The vulnerability could not be exploited remotely or by anonymous users.

Workarounds for Kernel Local Elevation of Privilege Vulnerability - CVE-2007-1206:

We have not identified any workarounds for this vulnerability.

FAQ for Kernel Local Elevation of Privilege Vulnerability - CVE-2007-1206:

Why is this bulletin being reoffered? 
Customers who are running Windows 2000 on NEC 98 machines may not have correctly received security update 931784. Microsoft has re-released this bulletin to resolve this issue. Only customers who are running NEC 98 machines are affected by this re-release, all other customers are not affected.

What is the scope of the vulnerability? 
A privilege elevation vulnerability exists in Windows Kernel because of incorrect permissions on a mapped memory segment. An attacker who successfully exploited this vulnerability could take complete control of an affected system. To attempt to exploit the vulnerability, an attacker must be able to log on locally to the system.

What causes the vulnerability? 
The Windows Kernel allows for incorrect permissions to be used when mapping a memory segment.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could run arbitrary code on a user’s system with elevated privileges. This could allow an attacker to take complete control of the affected system.

How could an attacker exploit the vulnerability? 
To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and gain complete control over the affected system.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

Could the vulnerability be exploited over the Internet? 
No. An attacker must be able to log on to the specific system that is targeted for attack. An attacker cannot load and run a program remotely by using this vulnerability.

What does the update do? 
The update removes the vulnerability by modifying the way that the Windows Kernel validates permissions during memory mapping.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.

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

Affected Software:

For information about the specific security update for your affected software, see the appropriate section:

Windows 2000 (all versions)

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

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

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

Inclusion in Future Service Packs
There are no more service packs planned for this operating system. The update for this issue may be included in a future update rollup.

Installation Information

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/helpDisplays the command-line options.
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed.
/forcerestartRestarts the computer after installation and forces other applications to close at shutdown without saving open files first.
/warnrestart[:x]Displays a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestartDisplay a dialog box prompting the local user to allow a restart.
Special Options
/overwriteoemOverwrites OEM files without prompting.
/nobackupDoes not back up files needed for uninstallation.
/forceappscloseForces other programs to close when the computer shuts down.
/log:pathAllows the redirection of installation log files.
/integrate:pathIntegrates 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.
/EREnables extended error reporting.
/verboseEnables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

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

Deployment Information

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

Windows2000-kb931784-x86-enu /quiet

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

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

Windows2000-kb931784-x86-enu /norestart

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

Restart Requirement

You must restart your system after you apply this security update. For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.

Removal Information

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

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

Supported Spuninst.exe Switches
SwitchDescription
/helpDisplays the command-line options.
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed.
/forcerestartRestarts the computer after installation and forces other applications to close at shutdown without saving open files first.
/warnrestart[:x]Displays a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestartDisplay a dialog box prompting the local user to allow a restart.
Special Options
/forceappscloseForces other programs to close when the computer shuts down.
/log:pathAllows the redirection of installation log files.

File Information

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

Windows 2000 Service Pack 4 and Small Business Server 2000:

File NameVersionDateTimeSize
Mup.sys5.0.2195.700602-Dec-200413:0789,328
Ntkrnlmp.exe5.0.2195.713305-Mar-200715:511,714,496
Ntkrnlpa.exe5.0.2195.713305-Mar-200715:521,713,536
Ntkrpamp.exe5.0.2195.713305-Mar-200715:521,735,808
Ntoskrnl.exe5.0.2195.713305-Mar-200715:511,690,880

Verifying that the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

    To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the frequently asked question, “Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine whether this update is required?” in the section, Frequently Asked Questions (FAQ) Related to This Security Update, earlier in this bulletin.

  • File Version Verification

    Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
    5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
  • Registry Key Verification

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

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB931784\Filelist

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

Windows XP (all versions)

Prerequisites
This security update requires Windows XP Service Pack 2. For more information on how to obtain the latest Windows XP service pack, see Microsoft Knowledge Base Article 322389. For more information on how to how to obtain Service Pack 2 for Windows XP Professional see the Download Center.

Inclusion in Future Service Packs
The update for this issue will be included in a future service pack or update rollup.

Installation Information

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/helpDisplays the command-line options.
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed.
/forcerestartRestarts the computer after installation and forces other applications to close at shutdown without saving open files first.
/warnrestart[:x]Displays a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestartDisplay a dialog box prompting the local user to allow a restart.
Special Options
/overwriteoemOverwrites OEM files without prompting.
/nobackupDoes not back up files needed for uninstallation.
/forceappscloseForces other programs to close when the computer shuts down.
/log:pathAllows the redirection of installation log files.
/integrate:pathIntegrates 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.
/EREnables extended error reporting.
/verboseEnables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

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

Deployment Information

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

Windowsxp-kb931784-x86-enu /quiet

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

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

Windowsxp-kb931784-x86-enu /norestart

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

Restart Requirement

You must restart your system after you apply this security update. For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.

Removal Information

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

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

Supported Spuninst.exe Switches
SwitchDescription
/helpDisplays the command-line options.
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed.
/forcerestartRestarts the computer after installation and forces other applications to close at shutdown without saving open files first.
/warnrestart[:x]Displays a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestartDisplay a dialog box prompting the local user to allow a restart.
Special Options
/forceappscloseForces other programs to close when the computer shuts down.
/log:pathAllows the redirection of installation log files.

File Information

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

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

File NameVersionDateTimeSizeFolder
Ntkrnlmp.exe5.1.2600.190815-Feb-200708:391,901,056SP1QFE
Ntkrnlpa.exe5.1.2600.190815-Feb-200708:391,955,968SP1QFE
Ntkrpamp.exe5.1.2600.190815-Feb-200708:391,929,216SP1QFE
Ntoskrnl.exe5.1.2600.190815-Feb-200714:522,040,704SP1QFE
Ntkrnlmp.exe5.1.2600.309328-Feb-200709:082,136,064SP2GDR
Ntkrnlpa.exe5.1.2600.309328-Feb-200708:382,057,600SP2GDR
Ntkrpamp.exe5.1.2600.309328-Feb-200708:382,015,744SP2GDR
Ntoskrnl.exe5.1.2600.309328-Feb-200709:102,180,352SP2GDR
Ntkrnlmp.exe5.1.2600.309328-Feb-200709:532,137,600SP2QFE
Ntkrnlpa.exe5.1.2600.309327-Feb-200719:452,059,392SP2QFE
Ntkrpamp.exe5.1.2600.309328-Feb-200709:152,017,280SP2QFE
Ntoskrnl.exe5.1.2600.309328-Feb-200709:552,182,144SP2QFE

Notes When you install these security updates, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

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

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

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

Verifying that the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

    To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the frequently asked question, “Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine whether this update is required?” in the section, Frequently Asked Questions (FAQ) Related to This Security Update, earlier in this bulletin.

  • File Version Verification

    Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
    5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
  • Registry Key Verification

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

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

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

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

Windows Server 2003 (all versions)

Prerequisites
This security update requires Windows Server 2003, Windows Server 2003 Service Pack 1, Windows Server 2003 Service Pack 2.

Inclusion in Future Service Packs
The update for this issue will be included in future service pack or update rollup.

Installation Information

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/helpDisplays the command-line options.
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed.
/forcerestartRestarts the computer after installation and forces other applications to close at shutdown without saving open files first.
/warnrestart[:x]Displays a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestartDisplay a dialog box prompting the local user to allow a restart.
Special Options
/overwriteoemOverwrites OEM files without prompting.
/nobackupDoes not back up files needed for uninstallation.
/forceappscloseForces other programs to close when the computer shuts down.
/log: pathAllows the redirection of installation log files.
/integrate:pathIntegrates 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.
/EREnables extended error reporting.
/verboseEnables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

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

Deployment Information

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

Windowsserver2003-kb931784-x86-enu /quiet

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

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

Windowsserver2003-kb931784-x86-enu /norestart

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

Restart Requirement

You must restart your system after you apply this security update. For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.

This security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341.

Removal Information

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

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

Supported Spuninst.exe Switches
SwitchDescription
/helpDisplays the command-line options.
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed.
/forcerestartRestarts the computer after installation and forces other applications to close at shutdown without saving open files first.
/warnrestart[:x]Displays a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestartDisplay a dialog box prompting the local user to allow a restart.
Special Options
/forceappscloseForces other programs to close when the computer shuts down.
/log:pathAllows the redirection of installation log files.

File Information

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

File NameVersionDateTimeSizeFolder
Ntkrnlmp.exe5.2.3790.65202-Mar-200709:142,233,856RTMGDR
Ntkrnlpa.exe5.2.3790.65202-Mar-200708:472,063,360RTMGDR
Ntkrpamp.exe5.2.3790.65202-Mar-200708:472,105,856RTMGDR
Ntoskrnl.exe5.2.3790.65202-Mar-200709:132,200,064RTMGDR
Ntkrnlmp.exe5.2.3790.65202-Mar-200709:312,240,512RTMQFE
Ntkrnlpa.exe5.2.3790.65202-Mar-200709:092,068,992RTMQFE
Ntkrpamp.exe5.2.3790.65202-Mar-200709:092,113,536RTMQFE
Ntoskrnl.exe5.2.3790.65202-Mar-200709:312,206,720RTMQFE
Srv.sys5.2.3790.58801-Sep-200610:14342,016RTMQFE
Ntkrnlmp.exe5.2.3790.289405-Mar-200709:402,452,480SP1GDR
Ntkrnlpa.exe5.2.3790.289405-Mar-200709:122,266,624SP1GDR
Ntkrpamp.exe5.2.3790.289405-Mar-200709:122,306,560SP1GDR
Ntoskrnl.exe5.2.3790.289405-Mar-200709:392,414,592SP1GDR
Ntkrnlmp.exe5.2.3790.289405-Mar-200709:562,459,648SP1QFE
Ntkrnlpa.exe5.2.3790.289405-Mar-200709:222,271,744SP1QFE
Ntkrpamp.exe5.2.3790.289405-Mar-200709:222,311,680SP1QFE
Ntoskrnl.exe5.2.3790.289405-Mar-200709:562,419,712SP1QFE
Ntkrnlmp.exe5.2.3790.403505-Mar-200713:052,469,888SP2GDR
Ntkrnlpa.exe5.2.3790.403505-Mar-200712:162,280,960SP2GDR
Ntkrpamp.exe5.2.3790.403505-Mar-200712:162,321,408SP2GDR
Ntoskrnl.exe5.2.3790.403505-Mar-200713:042,430,464SP2GDR
Ntkrnlmp.exe5.2.3790.403505-Mar-200706:012,469,376SP2QFE
Ntkrnlpa.exe5.2.3790.403505-Mar-200714:032,281,472SP2QFE
Ntkrpamp.exe5.2.3790.403505-Mar-200706:012,321,408SP2QFE
Ntoskrnl.exe5.2.3790.403505-Mar-200715:322,430,464SP2QFE

Windows Server 2003, Web Edition, Windows Server 2003, Standard Edition, Windows Server 2003, Datacenter Edition, Windows Server 2003, Enterprise Edition, Windows Small Business Server 2003, Windows Server 2003, Web Edition with SP1, Windows Server 2003, Standard Edition with SP1, Windows Server 2003, Enterprise Edition with SP1, Windows Server 2003, Datacenter Edition with SP1, Windows Server 2003, Web Edition with SP2, Windows Server 2003, Standard Edition with SP2, Windows Server 2003, Enterprise Edition with SP2, Windows Server 2003, Datacenter Edition with SP2, Windows Server 2003 R2, Web Edition, Windows Server 2003 R2, Standard Edition, Windows Server 2003 R2, Datacenter Edition, Windows Server 2003 R2, Enterprise Edition and Windows Small Business Server 2003 R2:

Notes When you install these security updates, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

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

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

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

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

Verifying that the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

    To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the frequently asked question, “Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine whether this update is required?” in the section, Frequently Asked Questions (FAQ) Related to This Security Update, earlier in this bulletin.

  • File Version Verification

    Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
    5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
  • Registry Key Verification

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

    Windows Server 2003, Web Edition, Windows Server 2003, Standard Edition, Windows Server 2003, Datacenter Edition, Windows Server 2003, Enterprise Edition, Windows Small Business Server 2003, Windows Server 2003, Web Edition with SP1, Windows Server 2003, Standard Edition with SP1, Windows Server 2003, Enterprise Edition with SP1, Windows Server 2003, Datacenter Edition with SP1, Windows Server 2003, Web Edition with SP2, Windows Server 2003, Standard Edition with SP2, Windows Server 2003, Enterprise Edition with SP2, Windows Server 2003, Datacenter Edition with SP2, Windows Server 2003 R2, Web Edition, Windows Server 2003 R2, Standard Edition, Windows Server 2003 R2, Datacenter Edition, Windows Server 2003 R2, Enterprise Edition and Windows Small Business Server 2003 R2:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB931784\Filelist

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

Other Information

Acknowledgments

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

  • eEye for reporting the Kernel Local Elevation of Privilege Vulnerability (CVE-2007-1206).

Obtaining Other Security Updates:

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

Support:

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

Security Resources:

Software Update Services:

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

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

Windows Server Update Services:

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

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

Systems Management Server:

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

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

Disclaimer:

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

Revisions:

  • V1.0 (April 10, 2007): Bulletin published.
  • V2.0 (June 26, 2007); Updated this bulletin to advise customers running Windows 2000 Service Pack 4 on NEC 98 systems that a revised version of the security update is available.

Built at 2014-04-16T02:39:51Z-07:00

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