Microsoft Security Bulletin MS08-005 - Important
Vulnerability in Internet Information Services Could Allow Elevation of Privilege (942831)
Published: | Updated:
Version: 1.1
General Information
Executive Summary
This important update resolves a privately reported vulnerability in Internet Information Services (IIS). A local 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. 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.
The security update is rated Important for Microsoft Internet Information Services 5.0 on Microsoft Windows 2000, Microsoft Internet Information Services 5.1 on Windows XP, Microsoft Internet Information Server 6.0 on Windows Server 2003, and Microsoft Internet Information Services 7.0 on Windows Vista. For more information, see the subsection, Affected and Non-Affected Software, in this section.
For more information about this vulnerability, see the Frequently Asked Questions (FAQ) subsection under the next section, Vulnerability Information.
Recommendation. Microsoft recommends that customers apply the update at the earliest opportunity.
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 Internet Information Services 5.0 | Elevation of Privilege | Important | None |
| Windows XP Professional Service Pack 2 | Microsoft Internet Information Services 5.1 | Elevation of Privilege | Important | None |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Microsoft Internet Information Services 6.0 | Elevation of Privilege | Important | None |
| Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Microsoft Internet Information Services 6.0 | Elevation of Privilege | Important | None |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Microsoft Internet Information Services 6.0 | Elevation of Privilege | Important | None |
| Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Microsoft Internet Information Services 6.0 | Elevation of Privilege | Important | None |
| Windows Vista | Microsoft Internet Information Services 7.0 | Elevation of Privilege | Important | None |
| Windows Vista x64 Edition | Microsoft Internet Information Services 7.0 | Elevation of Privilege | Important | None |
Non-Affected Software
| Operating System |
|---|
| Windows Vista Service Pack 1 (all editions) |
| Windows Server 2008 (all editions) |
Frequently Asked Questions (FAQ) Related to This Security Update
Which services are affected by this vulnerability on each Operating System?
The following table provides a list of each affected service per the affecte Operating System. Those services are World Wide Web Publishing Service (W3SVC), FTP Publishing Service (FTPSVC), and Network News Transport Protocol (NNTP). The only service that is enabled by default is W3SVC on Microsoft Windows 2000 Service Pack 4.
| Operating System | Service Affected |
|---|---|
| Microsoft Windows 2000 Service Pack 4 | W3SVC, FTPSVC, NNTPSVC |
| Windows XP Professional Service Pack 2 | W3SVC, FTPSVC |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | FTPSVC |
| Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | FTPSVC, NNTPSVC |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | FTPSVC, NNTPSVC |
| Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | FTPSVC, NNTPSVC |
| Windows Vista | FTPSVC |
| Windows Vista x64 Edition | FTPSVC |
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 have been tested to determine which versions or editions are affected. Other versions or editions are past their support life cycle. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.
It should be a priority for customers who have older versions or editions of the software to migrate to supported versions or editions 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 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 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 | File Change Notification Vulnerability - CVE-2008-0074 | Aggregate Severity Rating |
|---|---|---|
| Microsoft Internet Information Services (IIS) 5.0 on Microsoft Windows 2000 Service Pack 4 | Important Elevation of Privilege | Important |
| Microsoft Internet Information Services (IIS) 5.1 on Windows XP Professional Service Pack 2 | Important Elevation of Privilege | Important |
| Microsoft Internet Information Services (IIS) 6.0 on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Important Elevation of Privilege | Important |
| Microsoft Internet Information Services (IIS) 6.0 on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Important Elevation of Privilege | Important |
| Microsoft Internet Information Services (IIS) 6.0 on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Important Elevation of Privilege | Important |
| Microsoft Internet Information Services (IIS) 6.0 on Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Important Elevation of Privilege | Important |
| Microsoft Internet Information Services (IIS) 7.0 on Windows Vista | Important Elevation of Privilege | Important |
| Microsoft Internet Information Services (IIS) 7.0 on Windows Vista x64 Edition | Important Elevation of Privilege | Important |
File Change Notification Vulnerability - CVE-2008-0074
A local elevation of privilege vulnerability exists in the way that the Internet Information Service handles file change notifications in the FTPRoot, NNTPFile\Root, and WWWRoot folders. An attacker who successfully exploited this vulnerability could execute arbitrary code in the context of local system. An attacker could then install programs; view, change, or delete data; or create new accounts with full administrative rights.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-0074.
Mitigating Factors for File Change Notification Vulnerability - CVE-2008-0074
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:
- On Windows XP Professional Service Pack 2 and Windows Server 2003, the IUSR_MACHINENAME account (used for anonymous access) does not have write access to the WWW root folders by default.
- The specially crafted file or folder that would be required to exploit this vulnerability must be created locally. It could not be created through an FTP client connected to the FTP server service.
- On Windows XP, Windows Server 2003, and Windows Vista, IIS is not installed or enabled by default.
Workarounds for File Change Notification Vulnerability - CVE-2008-0074
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:
- On Windows Server 2003, stop the FTP and NNTP services
Exploitation of this vulnerability would require that the attacker have write access to the FTP root or NNTP root folders. By default the IIS anonymous access account, IUSR_MACHINENAME, has write access to the FTP root and NNTP root folders. Stopping these services will prevent the FTP and NNTP services from responding to change notifications for files in those directories. To stop the FTP and NNTP services, follow these steps:
From a command prompt, run the following commands:
net stop msftpsvc
net stop nntpsvcImpact of workaround. Users will be unable to use the FTP and NNTP services.
How to undo the workaround. To undo the workaround, follow these steps:
From a command prompt, run the following commands:
net start msftpsvc
net start nntpsvc - Deny write access to the NNTP root, FTP root, and WWW root folders for any accounts that are used to execute user controlled ASP pages.
Verify that the WWW root folder does not allow write access for any accounts used to execute user controlled ASP pages. To deny write access to the NNTP root, FTP root, and WWW root folders follow these steps:
Note The ACLs of the WWW root folder should be verified to ensure that anonymous access user accounts do not have write access.
Note The following commands will deny the IIS anonymous user account write access to the default FTP and NNTP root directories of a machine named WS2003ENTSP1.
From a command prompt, run the following commands:
cacls c:\inetpub\ftproot /E /P IUSR_WS2003ENTSP1:R
cacls c:\inetpub\ftproot /E /P USERS:R
cacls c:\inetpub\nntpfile\root /E /P "ANONYMOUS LOGON":R
cacls c:\inetpub\nntpfile\root /E /P EVERYONE:RImpact of workaround. Users will be denied write access to the NNTP root, FTP root, and WWW root folders for any accounts that are used to execute user-controlled ASP pages.
How to undo the workaround. Restore the ACLs on the folders to their previously configured setting.
FAQ for File Change Notification Vulnerability - CVE-2008-0074
What is the scope of the vulnerability?
This is a local elevation of privilege vulnerability. An attacker who successfully exploited this vulnerability could execute arbitrary code in the context of local system.
What causes the vulnerability?
The vulnerability exists in the way that the Internet Information Service handles the file change notifications in the FTPRoot, NNTPFile\Root, and WWWRoot folders.
What might an attacker use the vulnerability to do?
A local attacker could successfully exploit this vulnerability to gain full control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full administrative rights.
How could an attacker exploit the vulnerability?
A local attacker would have to be able to create or modify a file only in the FTPRoot, NNTPFile\Root, or WWWRoot directory. Virtual directories and sub-directories are not affected. A remote attacker would have to be able to upload a script to an affected IIS server, and be able to run the script. This uploaded script would need write access to the FTPRoot, NNTPFile\Root, or WWWRoot folders.
What systems are primarily at risk from the vulnerability?
Web hosting providers that allow their customers to upload ASP pages to their hosted web sites are primarily at risk from exploitation of this vulnerability. In addition, Microsoft Windows 2000 Service Pack 4 systems running IIS 5.0 are at risk from this vulnerability because IIS is enabled by default. Supported editions of Windows XP, Windows Server 2003, and Windows Vista are also at risk if the service is enabled.
What does the update do?
The update removes the vulnerability by modifying the way that the Internet Information Service handles file change notifications in the FTPRoot, NNTPFile\Root, and WWWRoot folders.
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.
Update Information
Detection and Deployment Tools and Guidance
Manage the software and security updates you need to deploy to the servers, desktop, and mobile computers 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.0.1 |
|---|---|
| Microsoft Internet Information Services (IIS) 5.0 on Microsoft Windows 2000 Service Pack 4 | Yes |
| Microsoft Internet Information Services (IIS) 5.1 on Windows XP Professional Service Pack 2 | Yes |
| Microsoft Internet Information Services (IIS) 6.0 on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Yes |
| Microsoft Internet Information Services (IIS) 6.0 on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Yes |
| Microsoft Internet Information Services (IIS) 6.0 on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Yes |
| Microsoft Internet Information Services (IIS) 6.0 on Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | No |
| Microsoft Internet Information Services (IIS) 7.0 on Windows Vista | See Note for Windows Vista below |
| Microsoft Internet Information Services (IIS) 7.0 on Windows Vista x64 Edition | See Note for Windows Vista below |
Note for Windows Vista Microsoft does not support installing MBSA 2.0.1 on computers that run Windows Vista, but you may install MBSA 2.0.1 on a supported operating system and then scan the Windows Vista-based computer remotely. For additional information about MBSA support for Windows Vista, visit the MBSA Web site. See also Microsoft Knowledge Base Article 931943: Microsoft Baseline Security Analyzer (MBSA) support for Windows Vista.
For more information about MBSA 2.0.1, see MBSA 2.0 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 | SCCM 2007 |
|---|---|---|---|
| Microsoft Internet Information Services (IIS) 5.0 on Microsoft Windows 2000 Service Pack 4 | Yes | Yes | Yes |
| Microsoft Internet Information Services (IIS) 5.1 on Windows XP Professional Service Pack 2 | Yes | Yes | Yes |
| Microsoft Internet Information Services (IIS) 6.0 on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | No | Yes | Yes |
| Microsoft Internet Information Services (IIS) 6.0 on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Yes | Yes | Yes |
| Microsoft Internet Information Services (IIS) 6.0 on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | No | Yes | Yes |
| Microsoft Internet Information Services (IIS) 6.0 on Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | No | Yes | Yes |
| Microsoft Internet Information Services (IIS) 7.0 on Windows Vista | No | See Note for Windows Vista below | Yes |
| Microsoft Internet Information Services (IIS) 7.0 on Windows Vista x64 Edition | No | See Note for Windows Vista below | Yes |
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. 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.
Note for Windows Vista Microsoft Systems Management Server 2003 with Service Pack 3 includes support for Windows Vista manageability.
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 Information
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 | Windows2000-KB942831-x86-enu /quiet |
| Installing without restarting | Windows2000-KB942831-x86-enu /norestart |
| Update log file | KB942831.log |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required | Yes, you must restart your system after you apply this security update |
| Hotpatching | Not applicable |
| Removal Information | Use Add or Remove Programs tool in Control Panel or the SP uninstall tool at %Windir%\$NTUninstallKB942831$\Spuninst |
| File Information | See the next subsection, File Information, for the full file manifest |
| Registry Key Verification | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB942831\Filelist |
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.
For all supported editions of Windows 2000:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| infocomm.dll | 5.0.2195.7147 | 10-Jan-2008 | 18:45 | 248,592 |
Note For a complete list of supported versions and editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.
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 | Display a dialog box prompting the local user to allow a restart |
| Special Options | |
| /overwriteoem | Overwrites OEM files without prompting |
| /nobackup | Does not back up files needed for uninstall |
| /forceappsclose | Forces other programs to close when the computer shuts down |
| /log:path | Allows the redirection of installation log files |
| /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 | Display a dialog box prompting the local user to allow a restart |
| Special Options | |
| /forceappsclose | Forces other programs to close when the computer shuts down |
| /log:path | Allows the redirection of installation log files |
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 | For all supported 32-bit editions of Windows XP: WindowsXP-KB942831-x86-enu /quiet |
| For all supported x64-based editions of Windows XP Professional : WindowsServer2003.WindowsXP-KB942831-x64-enu /quiet | |
| Installing without restarting | For all supported 32-bit editions of Windows XP: WindowsXP-KB942831-x86-enu /norestart |
| For all supported x64-based editions of Windows XP Professional: WindowsServer2003.WindowsXP-KB942831-x64-enu /norestart | |
| Update log file | KB942831.log |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required | Yes, you must restart your system after you apply this security update |
| Hotpatching | Not applicable |
| Removal Information | Use Add or Remove Programs tool in Control Panel or the SP uninstall tool at %Windir%\$NTUninstallKB942831$\Spuninst |
| File Information | See the next subsection, File Information, for the full file manifest |
| Registry Key Verification | For all supported 32-bit versions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB942831\Filelist |
| For all supported x64-based editions of Windows XP Professional: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB942831\Filelist |
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.
For all supported 32-bit editions of Windows XP:
| File Name | Version | Date | Time | Size | Folder |
|---|---|---|---|---|---|
| infocomm.dll | 6.0.2600.3290 | 10-Jan-2008 | 05:20 | 257,024 | SP2GDR |
| infocomm.dll | 6.0.2600.3290 | 10-Jan-2008 | 05:09 | 257,024 | SP2QFE |
For all supported x64-based editions of Windows XP Professional:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| infocomm.dll | 6.0.3790.3068 | 10-Jan-2008 | 18:54 | 344,064 | X64 | SP1GDR |
| infocomm.dll | 6.0.3790.3068 | 10-Jan-2008 | 18:53 | 338,944 | X64 | SP1QFE |
| infocomm.dll | 6.0.3790.4215 | 10-Jan-2008 | 19:02 | 338,944 | X64 | SP2GDR |
| infocomm.dll | 6.0.3790.4215 | 10-Jan-2008 | 18:54 | 338,944 | X64 | SP2QFE |
Note For a complete list of supported versions and editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.
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 | Display a dialog box prompting the local user to allow a restart |
| Special Options | |
| /overwriteoem | Overwrites OEM files without prompting |
| /nobackup | Does not back up files needed for uninstall |
| /forceappsclose | Forces other programs to close when the computer shuts down |
| /log:path | Allows the redirection of installation log files |
| /integrate:path | Integrates the update into the Windows source files. These files are located at the path that is specified in the switch. |
| /extract[:path] | Extracts files without starting the Setup program |
| /ER | Enables extended error reporting |
| /verbose | Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
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 | Display a dialog box prompting the local user to allow a restart |
| Special Options | |
| /forceappsclose | Forces other programs to close when the computer shuts down |
| /log:path | Allows the redirection of installation log files |
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 all supported 32-bit editions of Windows Server 2003: WindowsServer2003-KB942831-x86-enu /quiet |
| For all supported Itanium-based editions of Windows Server 2003: WindowsServer2003-KB942831-ia64-enu /quiet | |
| For all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB942831-x64-enu /quiet | |
| Installing without restarting | For all supported 32-bit editions of Windows Server 2003: WindowsServer2003-KB942831-x86-enu /norestart |
| For all supported Itanium-based editions of Windows Server 2003: WindowsServer2003-KB942831-ia64-enu /norestart | |
| For all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB942831-x64-enu /norestart | |
| Update log file | KB942831.log |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required | This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. |
| Hotpatching | 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 SP uninstall tool at %Windir%\$NTUninstallKB942831$\Spuninst |
| File Information | See the next subsection, File Information, for the full file manifest |
| Registry Key Verification | For all supported 32-bit editions, Itanium-based editions, and x64-based editions of Windows Server 2003: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB942831\Filelist |
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.
For all supported 32-bit editions of Windows Server 2003:
| File Name | Version | Date | Time | Size | Folder |
|---|---|---|---|---|---|
| infocomm.dll | 6.0.3790.3068 | 09-Jan-2008 | 18:24 | 238,592 | SP1GDR |
| infocomm.dll | 6.0.3790.3068 | 09-Jan-2008 | 18:59 | 235,520 | SP1QFE |
| infocomm.dll | 6.0.3790.4215 | 09-Jan-2008 | 19:37 | 235,520 | SP2GDR |
| infocomm.dll | 6.0.3790.4215 | 09-Jan-2008 | 20:10 | 235,520 | SP2QFE |
For all supported Itanium-based editions of Windows Server 2003:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| infocomm.dll | 6.0.3790.3068 | 10-Jan-2008 | 10:52 | 630,784 | IA-64 | SP1GDR |
| infocomm.dll | 6.0.3790.3068 | 10-Jan-2008 | 10:52 | 622,080 | IA-64 | SP1QFE |
| infocomm.dll | 6.0.3790.4215 | 10-Jan-2008 | 11:00 | 622,080 | IA-64 | SP2GDR |
| infocomm.dll | 6.0.3790.4215 | 10-Jan-2008 | 10:54 | 622,080 | IA-64 | SP2QFE |
For all supported x64-based editions of Windows Server 2003:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| infocomm.dll | 6.0.3790.3068 | 10-Jan-2008 | 18:54 | 344,064 | X64 | SP1GDR |
| infocomm.dll | 6.0.3790.3068 | 10-Jan-2008 | 18:53 | 338,944 | X64 | SP1QFE |
| infocomm.dll | 6.0.3790.4215 | 10-Jan-2008 | 19:02 | 338,944 | X64 | SP2GDR |
| infocomm.dll | 6.0.3790.4215 | 10-Jan-2008 | 18:54 | 338,944 | X64 | SP2QFE |
Note For a complete list of supported versions and editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.
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 | Display a dialog box prompting the local user to allow a restart |
| Special Options | |
| /overwriteoem | Overwrites OEM files without prompting |
| /nobackup | Does not back up files needed for uninstall |
| /forceappsclose | Forces other programs to close when the computer shuts down |
| /log:path | Allows the redirection of installation log files |
| /integrate:path | Integrates the update into the Windows source files. These files are located at the path that is specified in the switch. |
| /extract[:path] | Extracts files without starting the Setup program |
| /ER | Enables extended error reporting |
| /verbose | Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
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 | Display a dialog box prompting the local user to allow a restart |
| Special Options | |
| /forceappsclose | Forces other programs to close when the computer shuts down |
| /log:path | Allows the redirection of installation log files |
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 Vista (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
| Deployment | |
| Installing without user intervention | All supported 32-bit editions of Windows Vista: Windows6.0-KB942831-x86 /quiet |
| All supported x64-based editions of Windows Vista: Windows6.0-KB942831-x64 /quiet | |
| Installing without restarting | All supported 32-bit editions of Windows Vista: Windows6.0-KB942831-x86 /quiet /norestart |
| All supported x64-based editions of Windows Vista: Windows6.0-KB942831-x64 /quiet /norestart | |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required | Yes, you must restart your system after you apply this security update |
| Hotpatching | Not applicable |
| Removal Information | WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates. |
| File Information | See the next subsection, File Information, for the full file manifest. |
| Registry Key Verification | Note: A registry key does not exist to validate the presence of this update. To detect the presence of the update, use Windows Management Instrumentation (WMI). |
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.
For all supported 32-bit editions of Windows Vista:
| File Name | Version | Date | Time | Size | Folder |
|---|---|---|---|---|---|
| abocomp.dll | 7.0.6000.16576 | 11-Oct-2007 | 03:06 | 157,696 | x86_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_3706099124ffef2f |
| coadmin.dll | 7.0.6000.16576 | 11-Oct-2007 | 03:06 | 74,240 | x86_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_3706099124ffef2f |
| iisadmin.dll | 7.0.6000.16576 | 11-Oct-2007 | 03:07 | 15,872 | x86_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_3706099124ffef2f |
| iiscfg.dll | 7.0.6000.16576 | 11-Oct-2007 | 03:07 | 991,232 | x86_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_3706099124ffef2f |
| inetinfo.exe | 7.0.6000.16576 | 11-Oct-2007 | 01:41 | 13,824 | x86_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_3706099124ffef2f |
| infoadmn.dll | 7.0.6000.16576 | 11-Oct-2007 | 03:07 | 16,384 | x86_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_3706099124ffef2f |
| infocomm.dll | 7.0.6000.16576 | 11-Oct-2007 | 03:07 | 227,840 | x86_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_3706099124ffef2f |
| infoctrs.dll | 7.0.6000.16576 | 11-Oct-2007 | 03:07 | 9,728 | x86_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_3706099124ffef2f |
| isatq.dll | 7.0.6000.16576 | 11-Oct-2007 | 03:07 | 55,296 | x86_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_3706099124ffef2f |
| iscomlog.dll | 7.0.6000.16576 | 11-Oct-2007 | 03:07 | 19,968 | x86_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_3706099124ffef2f |
| metadata.dll | 7.0.6000.16576 | 11-Oct-2007 | 03:07 | 267,776 | x86_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_3706099124ffef2f |
| rpcref.dll | 7.0.6000.16576 | 11-Oct-2007 | 03:08 | 7,680 | x86_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_3706099124ffef2f |
| wamreg.dll | 7.0.6000.16576 | 11-Oct-2007 | 03:09 | 55,808 | x86_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_3706099124ffef2f |
| abocomp.dll | 7.0.6000.20698 | 11-Oct-2007 | 03:05 | 157,696 | x86_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_377c07183e2bf989 |
| coadmin.dll | 7.0.6000.20698 | 11-Oct-2007 | 03:05 | 74,240 | x86_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_377c07183e2bf989 |
| iisadmin.dll | 7.0.6000.20698 | 11-Oct-2007 | 03:06 | 15,872 | x86_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_377c07183e2bf989 |
| iiscfg.dll | 7.0.6000.20698 | 11-Oct-2007 | 03:06 | 991,232 | x86_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_377c07183e2bf989 |
| inetinfo.exe | 7.0.6000.20698 | 11-Oct-2007 | 01:43 | 13,824 | x86_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_377c07183e2bf989 |
| infoadmn.dll | 7.0.6000.20698 | 11-Oct-2007 | 03:06 | 16,384 | x86_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_377c07183e2bf989 |
| infocomm.dll | 7.0.6000.20698 | 11-Oct-2007 | 03:06 | 227,840 | x86_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_377c07183e2bf989 |
| infoctrs.dll | 7.0.6000.20698 | 11-Oct-2007 | 03:06 | 9,728 | x86_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_377c07183e2bf989 |
| isatq.dll | 7.0.6000.20698 | 11-Oct-2007 | 03:06 | 55,296 | x86_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_377c07183e2bf989 |
| iscomlog.dll | 7.0.6000.20698 | 11-Oct-2007 | 03:06 | 19,968 | x86_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_377c07183e2bf989 |
| metadata.dll | 7.0.6000.20698 | 11-Oct-2007 | 03:06 | 267,776 | x86_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_377c07183e2bf989 |
| rpcref.dll | 7.0.6000.20698 | 11-Oct-2007 | 03:07 | 7,680 | x86_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_377c07183e2bf989 |
| wamreg.dll | 7.0.6000.20698 | 11-Oct-2007 | 03:08 | 55,808 | x86_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_377c07183e2bf989 |
For all supported x64-based editions of Windows Vista:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| abocomp.dll | 7.0.6000.16576 | 11-Oct-2007 | 04:14 | 174,080 | X64 | amd64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_9324a514dd5d6065 |
| coadmin.dll | 7.0.6000.16576 | 11-Oct-2007 | 04:15 | 81,408 | X64 | amd64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_9324a514dd5d6065 |
| iisadmin.dll | 7.0.6000.16576 | 11-Oct-2007 | 04:15 | 18,944 | X64 | amd64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_9324a514dd5d6065 |
| iiscfg.dll | 7.0.6000.16576 | 11-Oct-2007 | 04:15 | 1,057,280 | X64 | amd64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_9324a514dd5d6065 |
| inetinfo.exe | 7.0.6000.16576 | 11-Oct-2007 | 02:18 | 15,872 | X64 | amd64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_9324a514dd5d6065 |
| infoadmn.dll | 7.0.6000.16576 | 11-Oct-2007 | 04:16 | 22,528 | X64 | amd64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_9324a514dd5d6065 |
| infocomm.dll | 7.0.6000.16576 | 11-Oct-2007 | 04:16 | 269,824 | X64 | amd64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_9324a514dd5d6065 |
| infoctrs.dll | 7.0.6000.16576 | 11-Oct-2007 | 04:16 | 12,288 | X64 | amd64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_9324a514dd5d6065 |
| isatq.dll | 7.0.6000.16576 | 11-Oct-2007 | 04:16 | 64,512 | X64 | amd64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_9324a514dd5d6065 |
| iscomlog.dll | 7.0.6000.16576 | 11-Oct-2007 | 04:16 | 23,040 | X64 | amd64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_9324a514dd5d6065 |
| metadata.dll | 7.0.6000.16576 | 11-Oct-2007 | 04:16 | 284,160 | X64 | amd64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_9324a514dd5d6065 |
| rpcref.dll | 7.0.6000.16576 | 11-Oct-2007 | 04:17 | 9,216 | X64 | amd64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_9324a514dd5d6065 |
| wamreg.dll | 7.0.6000.16576 | 11-Oct-2007 | 04:18 | 66,560 | X64 | amd64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_9324a514dd5d6065 |
| abocomp.dll | 7.0.6000.20698 | 11-Oct-2007 | 04:00 | 174,080 | X64 | amd64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_939aa29bf6896abf |
| coadmin.dll | 7.0.6000.20698 | 11-Oct-2007 | 04:01 | 81,408 | X64 | amd64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_939aa29bf6896abf |
| iisadmin.dll | 7.0.6000.20698 | 11-Oct-2007 | 04:01 | 18,944 | X64 | amd64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_939aa29bf6896abf |
| iiscfg.dll | 7.0.6000.20698 | 11-Oct-2007 | 04:01 | 1,057,280 | X64 | amd64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_939aa29bf6896abf |
| inetinfo.exe | 7.0.6000.20698 | 11-Oct-2007 | 02:12 | 15,872 | X64 | amd64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_939aa29bf6896abf |
| infoadmn.dll | 7.0.6000.20698 | 11-Oct-2007 | 04:01 | 22,528 | X64 | amd64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_939aa29bf6896abf |
| infocomm.dll | 7.0.6000.20698 | 11-Oct-2007 | 04:01 | 269,824 | X64 | amd64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_939aa29bf6896abf |
| infoctrs.dll | 7.0.6000.20698 | 11-Oct-2007 | 04:01 | 12,288 | X64 | amd64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_939aa29bf6896abf |
| isatq.dll | 7.0.6000.20698 | 11-Oct-2007 | 04:01 | 64,512 | X64 | amd64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_939aa29bf6896abf |
| iscomlog.dll | 7.0.6000.20698 | 11-Oct-2007 | 04:01 | 23,040 | X64 | amd64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_939aa29bf6896abf |
| metadata.dll | 7.0.6000.20698 | 11-Oct-2007 | 04:02 | 284,160 | X64 | amd64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_939aa29bf6896abf |
| rpcref.dll | 7.0.6000.20698 | 11-Oct-2007 | 04:03 | 9,216 | X64 | amd64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_939aa29bf6896abf |
| wamreg.dll | 7.0.6000.20698 | 11-Oct-2007 | 04:03 | 66,560 | X64 | amd64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_939aa29bf6896abf |
| abocomp.dll | 7.0.6000.16576 | 11-Oct-2007 | 03:06 | 157,696 | X86 | wow64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_9d794f6711be2260 |
| coadmin.dll | 7.0.6000.16576 | 11-Oct-2007 | 03:06 | 74,240 | X86 | wow64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_9d794f6711be2260 |
| iisadmin.dll | 7.0.6000.16576 | 11-Oct-2007 | 03:07 | 15,872 | X86 | wow64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_9d794f6711be2260 |
| iiscfg.dll | 7.0.6000.16576 | 11-Oct-2007 | 03:07 | 991,232 | X86 | wow64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_9d794f6711be2260 |
| infoadmn.dll | 7.0.6000.16576 | 11-Oct-2007 | 03:07 | 16,384 | X86 | wow64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_9d794f6711be2260 |
| infocomm.dll | 7.0.6000.16576 | 11-Oct-2007 | 03:07 | 227,840 | X86 | wow64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_9d794f6711be2260 |
| infoctrs.dll | 7.0.6000.16576 | 11-Oct-2007 | 03:07 | 9,728 | X86 | wow64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_9d794f6711be2260 |
| isatq.dll | 7.0.6000.16576 | 11-Oct-2007 | 03:07 | 55,296 | X86 | wow64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_9d794f6711be2260 |
| iscomlog.dll | 7.0.6000.16576 | 11-Oct-2007 | 03:07 | 19,968 | X86 | wow64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_9d794f6711be2260 |
| metadata.dll | 7.0.6000.16576 | 11-Oct-2007 | 03:07 | 267,776 | X86 | wow64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_9d794f6711be2260 |
| rpcref.dll | 7.0.6000.16576 | 11-Oct-2007 | 03:08 | 7,680 | X86 | wow64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_9d794f6711be2260 |
| wamreg.dll | 7.0.6000.16576 | 11-Oct-2007 | 03:09 | 55,808 | X86 | wow64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.16576_none_9d794f6711be2260 |
| abocomp.dll | 7.0.6000.20698 | 11-Oct-2007 | 03:05 | 157,696 | X86 | wow64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_9def4cee2aea2cba |
| coadmin.dll | 7.0.6000.20698 | 11-Oct-2007 | 03:05 | 74,240 | X86 | wow64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_9def4cee2aea2cba |
| iisadmin.dll | 7.0.6000.20698 | 11-Oct-2007 | 03:06 | 15,872 | X86 | wow64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_9def4cee2aea2cba |
| iiscfg.dll | 7.0.6000.20698 | 11-Oct-2007 | 03:06 | 991,232 | X86 | wow64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_9def4cee2aea2cba |
| infoadmn.dll | 7.0.6000.20698 | 11-Oct-2007 | 03:06 | 16,384 | X86 | wow64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_9def4cee2aea2cba |
| infocomm.dll | 7.0.6000.20698 | 11-Oct-2007 | 03:06 | 227,840 | X86 | wow64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_9def4cee2aea2cba |
| infoctrs.dll | 7.0.6000.20698 | 11-Oct-2007 | 03:06 | 9,728 | X86 | wow64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_9def4cee2aea2cba |
| isatq.dll | 7.0.6000.20698 | 11-Oct-2007 | 03:06 | 55,296 | X86 | wow64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_9def4cee2aea2cba |
| iscomlog.dll | 7.0.6000.20698 | 11-Oct-2007 | 03:06 | 19,968 | X86 | wow64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_9def4cee2aea2cba |
| metadata.dll | 7.0.6000.20698 | 11-Oct-2007 | 03:06 | 267,776 | X86 | wow64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_9def4cee2aea2cba |
| rpcref.dll | 7.0.6000.20698 | 11-Oct-2007 | 03:07 | 7,680 | X86 | wow64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_9def4cee2aea2cba |
| wamreg.dll | 7.0.6000.20698 | 11-Oct-2007 | 03:08 | 55,808 | X86 | wow64_microsoft-windows-iis-metabase_31bf3856ad364e35_6.0.6000.20698_none_9def4cee2aea2cba |
Note For a complete list of supported versions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.
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.
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 |
|---|---|
| /?, /h, /help | Displays help on supported switches. |
| /quiet | Suppresses the display of status or error messages. |
| /norestart | When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation. |
Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.
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 versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed. - On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
Other Information
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 (February 12, 2008) Bulletin published.
- V1.1 (February 13, 2008) Bulletin updated: Corrected the download link reference for Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 to reference Internet Information Services 6.0. The download link correctly directed customers to the IIS 6.0 update but the reference link incorrectly stated IIS 5.1.