Microsoft Security Bulletin MS09-020 - Important
Vulnerabilities in Internet Information Services (IIS) Could Allow Elevation of Privilege (970483)
Published: | Updated:
Version: 1.1
General Information
Executive Summary
This security update resolves one publicly disclosed vulnerability and one privately reported vulnerability in Microsoft Internet Information Services (IIS). The vulnerabilities could allow elevation of privilege if an attacker sent a specially crafted HTTP request to a Web site that requires authentication. These vulnerabilities allow an attacker to bypass the IIS configuration that specifies which type of authentication is allowed, but not the file system-based access control list (ACL) check that verifies whether a file is accessible by a given user. Successful exploitation of these vulnerabilities would still restrict the attacker to the permissions granted to the anonymous user account by the file system ACLs.
This security update is rated Important for Microsoft Internet Information Services on all supported editions of Microsoft Windows 2000, Windows XP, and Windows Server 2003. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The security update addresses the vulnerabilities by modifying the way that the WebDAV extension for IIS handles HTTP requests. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
This security update addresses the vulnerability described in Microsoft Security Advisory 971492.
Recommendation. The majority of customers have automatic updating enabled and will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.
For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update at the earliest opportunity using update management software, or by checking for updates using the Microsoft Update service.
See also the section, Detection and Deployment Tools and Guidance, later in this bulletin.
Known Issues. None
Affected and Non-Affected Software
The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.
Affected Software
| 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 and Windows XP Professional Service Pack 3 | Microsoft Internet Information Services 5.1 | Elevation of Privilege | Important | None |
| Windows XP Professional x64 Edition Service Pack 2 | Microsoft Internet Information Services 6.0 | Elevation of Privilege | Important | None |
| Windows Server 2003 Service Pack 2 | Microsoft Internet Information Services 6.0 | Elevation of Privilege | Important | None |
| Windows Server 2003 x64 Edition Service Pack 2 | Microsoft Internet Information Services 6.0 | Elevation of Privilege | Important | None |
| Windows Server 2003 with SP2 for Itanium-based Systems | Microsoft Internet Information Services 6.0 | Elevation of Privilege | Important | None |
Non-Affected Software
| Operating System | Component |
|---|---|
| Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2 | Microsoft Internet Information Services 7.0 |
| Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2 | Microsoft Internet Information Services 7.0 |
| Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2 | Microsoft Internet Information Services 7.0 |
| Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2 | Microsoft Internet Information Services 7.0 |
| Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 | Microsoft Internet Information Services 7.0 |
Frequently Asked Questions (FAQ) Related to This Security Update
Where are the file information details?
Refer to the reference tables in the Security Update Deployment section for the location of the file information details.
Why does this update address several reported security vulnerabilities?
This update contains support for several vulnerabilities because the modifications that are required to address these issues are located in related files. Instead of having to install several updates that are almost the same, customers need to install this update only.
I am using an older release of the software discussed in this security bulletin. What should I do?
The affected software listed in this bulletin have been tested to determine which releases are affected. Other releases are past their support life cycle. To determine the support life cycle for your software release, visit Microsoft Support Lifecycle.
It should be a priority for customers who have older releases of the software to migrate to supported releases to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit Microsoft Support Lifecycle. For more information about the extended security update support period for these software versions or editions, visit Microsoft Product Support Services.
Customers who require custom support for older releases must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit Microsoft Worldwide Information, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ.
Vulnerability Information
Severity Ratings and Vulnerability Identifiers
The following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin's release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the June bulletin summary. For more information, see Microsoft Exploitability Index.
| Affected Software | IIS 5.0 WebDAV Authentication Bypass Vulnerability - CVE-2009-1122 | IIS 5.1 and 6.0 WebDAV Authentication Bypass Vulnerability - CVE-2009-1535 | Aggregate Severity Rating |
|---|---|---|---|
| Microsoft Internet Information Services (IIS) 5.0 on Microsoft Windows 2000 Service Pack 4 | Important Elevation of Privilege | Not applicable | Important |
| Microsoft Internet Information Services (IIS) 5.1 on Windows XP Professional Service Pack 2 and Windows XP Professional Service Pack 3 | Not applicable | Important Elevation of Privilege | Important |
| Microsoft Internet Information Services (IIS) 6.0 on Windows XP Professional x64 Edition Service Pack 2 | Not applicable | Important Elevation of Privilege | Important |
| Microsoft Internet Information Services (IIS) 6.0 on Windows Server 2003 Service Pack 2 | Not applicable | Important Elevation of Privilege | Important |
| Microsoft Internet Information Services (IIS) 6.0 on Windows Server 2003 x64 Edition Service Pack 2 | Not applicable | Important Elevation of Privilege | Important |
| Microsoft Internet Information Services (IIS) 6.0 on Windows Server 2003 with SP2 for Itanium-based Systems | Not applicable | Important Elevation of Privilege | Important |
IIS 5.0 WebDAV Authentication Bypass Vulnerability - CVE-2009-1122
An elevation of privilege vulnerability exists in the way that the WebDAV extension for IIS handles HTTP requests. An attacker could exploit this vulnerability by creating a specially crafted anonymous HTTP request to gain access to a location that should require authentication.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-1122.
Mitigating Factors for IIS 5.0 WebDAV Authentication Bypass Vulnerability - CVE-2009-1122
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:
- Microsoft Internet Information Services versions 5.1, 6.0, and 7.0 are not affected by this vulnerability.
- The anonymous user account is denied write access by default. In order to successfully exploit this vulnerability with write access, the anonymous user account would need to have write access ACLs set within the IIS folder structure. However, by default, the anonymous user account only has read access ACLs set. On IIS 6.0, there is an explicit deny access control entry (ACE) for write permissions for the default anonymous user account. Unless overridden by the administrator, this deny ACE will be inherited by all children under the default Web site root.
- File system ACLs are enforced. This vulnerability allows for an attacker to bypass the IIS configuration that specifies which type of authentication is allowed, but not the file system-based ACL check that verifies whether a file is accessible by a given user. Successful exploitation of the vulnerability would still restrict the attacker to the permissions granted to the anonymous user account on the file system ACL level. Therefore this vulnerability cannot be used to exceed the level of access granted to the anonymous user account through file system ACLs. The default anonymous user account is configured as the IUSR_<computername> account.
Workarounds for IIS 5.0 WebDAV Authentication Bypass Vulnerability - CVE-2009-1122
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:
- Disable WebDAV
If WebDAV functionality is not required on the server, it can be disabled.
For IIS 5.0, WebDAV can be disabled as described in Microsoft Knowledge Base Article 241520.
Impact of workaround. After applying this workaround, WebDAV requests will not be served by IIS.
- Alternate method to disable WebDAV on IIS 5.0
The IIS Lockdown Tool 2.1 can be used to disable WebDAV as well. See Microsoft Knowledge Base Article 325864.
- To start the installation immediately, click Open or Run this program from its current location.
- To copy the download to your computer for installation at a later time, click Save or Save this program to disk.
Impact of workaround. This method achieves its results by installing UrlScan. By default, UrlScan blocks requests to WebDAV by detecting either HTTP verbs or headers that would be mapped to WebDAV. If the IIS Lockdown tool is uninstalled, UrlScan will remain. To uninstall UrlScan, unregister the UrlScan ISAPI filter from the IIS Manager snap-in.
- Change file system ACLs to deny access to the anonymous user account
If WebDAV functionality is required, NTFS ACLs should be used to control access to resources on the server. If resources should be inaccessible to the anonymous user through WebDAV, appropriate read or write NTFS ACLs should be applied based on desired access to that resource. For more information on setting ACLs for IIS content, see the following articles:
Impact of workaround. Applying this workaround may have adverse effects on products that require content to be accessed by the IUSR_<computername> account. Examples of these products include System Center Configuration Manager 2007.
FAQ for IIS 5.0 WebDAV Authentication Bypass Vulnerability - CVE-2009-1122
What is the scope of the vulnerability?
This is an elevation of privilege vulnerability that could allow an attacker to bypass an authentication requirement to access content on an IIS Server.
What causes the vulnerability?
The WebDAV extension does not properly decode a specially crafted requested URL. This causes WebDAV to apply an incorrect configuration when handling the request. If the applied configuration allows anonymous access, a specially crafted request can bypass authentication. In addition, because WebDAV applies an incorrect configuration, other settings in the IIS configuration that should be applied to a particular path, such as IP address restrictions, may not be honored by WebDAV.
Note that IIS would still process such a request in the security context of the configured anonymous user account. Therefore, this vulnerability cannot be used to bypass NTFS ACLs. The restrictions imposed on the anonymous user account by file system ACLs will still be enforced.
What is the anonymous user account?
When Web sites and applications running on the Web server require anonymous access, IIS must be configured with a user account specifically for anonymous access. This account will then be used to access content on the file system when requested by the anonymous Web user. In a default configuration, IIS uses the anonymous user account IUSR_<computername>, where <computername> is the name of the computer on which IIS is running. However, it is possible to change the anonymous user identity to use a different local user account or a domain user account as the anonymous user account.
What is WebDAV?
Web Distributed Authoring and Versioning (WebDAV) is an extension to the Hypertext Transfer Protocol (HTTP) that defines how basic file functions such as copy, move, delete and create are performed by a computer using HTTP.
What is an access control list (ACL)?
An access control list (ACL) is a list of security protections that applies to an object. (An object can be a file, process, event, or anything else having a security descriptor.) An entry in an ACL is an access control entry (ACE). There are two types of access control list, discretionary and system. Each ACE in an ACL identifies access rights allowed, denied, or audited for that trustee. For information, see the MSDN article, Access Control Lists.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability would be able to bypass the IIS configuration that specifies which type of authentication is allowed, but not the file system-based ACL check that verifies whether a file is accessible by a given user. Successful exploitation of the vulnerability would restrict the attacker to the permissions granted to the anonymous user account on file system ACL level. This could allow an attacker to anonymously access information that should only be accessible to an authenticated user, or write files to locations where the anonymous user account is granted write permission.
How could an attacker exploit the vulnerability?
An attacker could exploit the vulnerability by creating a specially crafted HTTP request to a Web site that requires authentication, and thereby gain unauthorized access to protected resources.
What systems are primarily at risk from the vulnerability?
Microsoft Windows 2000 systems on which IIS version 5.0 is used and where WebDAV is enabled are primarily at risk. Typically these are Web servers or application servers, but they may also be developer or Web designer or other workstation systems on which IIS is used with WebDAV. Systems that deviate from the default configuration in that the anonymous user account has been granted write permission are at increased risk.
What does the update do?
The update addresses the vulnerability by modifying the way that the WebDAV extension for IIS handles HTTP requests.
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.
IIS 5.1 and 6.0 WebDAV Authentication Bypass Vulnerability - CVE-2009-1535
An elevation of privilege vulnerability exists in the way that the WebDAV extension for IIS handles HTTP requests. An attacker could exploit this vulnerability by creating a specially crafted anonymous HTTP request to gain access to a location that typically requires authentication.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-1535.
Mitigating Factors for IIS 5.1 and 6.0 WebDAV Authentication Bypass Vulnerability - CVE-2009-1535
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:
- Microsoft Internet Information Server versions 5.0 and 7.0 are not affected by this vulnerability.
- WebDAV is not enabled by default on IIS 6.0. On IIS 6.0 running on Windows Server 2003 systems, WebDAV is not enabled in the default configuration. Unless WebDAV has been enabled by an administrator on these systems, the vulnerability is not exposed.
- The anonymous user account is denied write access by default. In order to successfully exploit this vulnerability with write access, the anonymous user account would need to have write access ACLs set within the IIS folder structure. However, by default, the anonymous user account only has read access ACLs set. On IIS 6.0, there is an explicit deny ACE for the default anonymous user account. Unless overridden by the administrator, this deny ACE will be inherited by all children under the default Web site root.
- File system ACLs are enforced. This vulnerability allows an attacker to bypass the IIS configuration that specifies which type of authentication is allowed, but not the file system-based ACL check that verifies whether a file is accessible by a given user. Successful exploitation of the vulnerability would still restrict the attacker to the permissions granted to the anonymous user account at the file system ACL level. Therefore this vulnerability cannot be used to exceed the level of access granted to the anonymous user account through file system ACLs. The default anonymous user account is configured as the IUSR_<computername> account.
Workarounds for IIS 5.1 and 6.0 WebDAV Authentication Bypass Vulnerability - CVE-2009-1535
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:
- Disable WebDAV
If WebDAV functionality is not required on the server, it can be disabled.
For IIS 5.0 and IIS 5.1, WebDAV can be disabled as described in Microsoft Knowledge Base Article 241520.
For IIS 6.0, WebDAV can be disabled using the following steps:
- Launch the IIS Manager MMC snap-in.
- In the left-hand pane, expand the local computer icon.
- Click on Web Service Extensions beneath this item.
- In the right-hand pane, select WebDAV and click the Prohibit button.
Impact of workaround. After applying this workaround, WebDAV requests will not be served by IIS.
- Alternate method to disable WebDAV on IIS 5.1 and IIS 6.0
Microsoft UrlScan Filter v3.1 can be used to disable WebDAV as well.
For IIS 5.1 and IIS 6.0, download Microsoft UrlScan Filter v3.1 from one of the following:
- For 32-bit systems: Microsoft Urlscan Filter v3.1 (x86)
- For x64-based systems: Microsoft Urlscan Filter v3.1 (x64)
Then do one of the following:
- To start the installation immediately, click Open or Run this program from its current location.
- To copy the download to your computer for installation at a later time, click Save or Save this program to disk.
Impact of workaround. This method achieves its results by installing UrlScan. By default, UrlScan blocks requests to WebDAV by detecting either HTTP verbs or headers that would be mapped to WebDAV.
- Change file system ACLs to deny access to the anonymous user account
If WebDAV functionality is required, NTFS ACLs should be used to control access to resources on the server. If resources should be inaccessible to the anonymous user through WebDAV, appropriate read or write NTFS ACLs should be applied based on desired access to that resource. For more information on setting ACLs for IIS content, see the following articles:
Impact of workaround. Applying this workaround may have adverse effects on products that require content to be accessed by the IUSR_<computername> account. Examples of these products include System Center Configuration Manager 2007.
FAQ for IIS 5.1 and 6.0 WebDAV Authentication Bypass Vulnerability - CVE-2009-1535
What is the scope of the vulnerability?
This is an elevation of privilege vulnerability that could allow an attacker to bypass an authentication requirement to access content on an IIS server.
What causes the vulnerability?
The WebDAV extension does not properly decode a specially crafted requested URL. This causes WebDAV to apply an incorrect configuration when handling the request. If the applied configuration allows anonymous access, a specially crafted request can bypass authentication. In addition, because WebDAV applies an incorrect configuration, other settings in the IIS configuration that should be applied to a particular path, such as IP address restrictions, may not be honored by WebDAV.
Note that IIS would still process such a request in the security context of the configured anonymous user account. Therefore, this vulnerability cannot be used to bypass NTFS ACLs. The restrictions imposed on the anonymous user account by file system ACLs will still be enforced.
What is the anonymous user account?
When Web sites and applications running on the Web server require anonymous access, IIS must be configured with a user account specifically for anonymous access. This account will then be used to access content on the file system when requested by the anonymous Web user. In a default configuration, IIS uses the anonymous user account IUSR_<computername>, where <computername> is the name of the computer on which IIS is running. However, it is possible to change the anonymous user identity to use a different local user account or a domain user account as the anonymous user account.
What is WebDAV?
Web Distributed Authoring and Versioning (WebDAV) is an extension to the Hypertext Transfer Protocol (HTTP) that defines how basic file functions such as copy, move, delete and create are performed by a computer using HTTP.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability would be able to bypass the IIS configuration that specifies which type of authentication is allowed, but not the file system-based ACL check that verifies whether a file is accessible by a given user. Successful exploitation of the vulnerability would restrict the attacker to the permissions granted to the anonymous user account on the file system ACL level. This could allow an attacker to anonymously access information that should only be accessible to an authenticated user, or write files to locations where the anonymous user account is granted write permission.
How could an attacker exploit the vulnerability?
An attacker could exploit the vulnerability by creating a specially crafted HTTP request to a Web site that requires authentication, and thereby gain unauthorized access to protected resources.
What systems are primarily at risk from the vulnerability?
Windows XP and Windows Server 2003 systems on which IIS version 5.1 or 6.0 is used and where WebDAV is enabled are primarily at risk. Typically these systems are Web servers or application servers, but they may also be developer or Web designer or other workstation systems on which IIS is used with WebDAV. Systems that deviate from the default configuration in that the anonymous user account has been granted write permission are at increased risk.
What does the update do?
The update addresses the vulnerability by modifying the way that the WebDAV extension for IIS handles HTTP requests.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. This vulnerability has been publicly disclosed. This vulnerability was first described in Microsoft Security Advisory 971492 as Common Vulnerability and Exposure number CVE-2009-1535. This vulnerability has also been assigned Common Vulnerability and Exposure number CVE-2009-1676.
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 systems in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.
Security updates are available from Microsoft Update, Windows Update, and Office Update. Security updates are also available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update."
Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, "MS07-036"), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ.
Detection and Deployment Guidance
Microsoft has provided detection and deployment guidance for this month’s security updates. This guidance will also help IT professionals understand how they can use various tools to help deploy the security update, such as Windows Update, Microsoft Update, Office Update, the Microsoft Baseline Security Analyzer (MBSA), the Office Detection Tool, Microsoft Systems Management Server (SMS), and the Extended Security Update Inventory Tool. For more information, see Microsoft Knowledge Base Article 910723.
Microsoft Baseline Security Analyzer
Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA, visit Microsoft Baseline Security Analyzer.
The following table provides the MBSA detection summary for this security update.
| Software | MBSA 2.1 |
|---|---|
| Microsoft Windows 2000 Service Pack 4 | Yes |
| Windows XP Professional Service Pack 2 and Windows XP Professional Service Pack 3 | Yes |
| Windows XP Professional x64 Edition Service Pack 2 | Yes |
| Windows Server 2003 Service Pack 2 | Yes |
| Windows Server 2003 x64 Edition Service Pack 2 | Yes |
| Windows Server 2003 with SP2 for Itanium-based Systems | Yes |
For more information about MBSA 2.1, see MBSA 2.1 Frequently Asked Questions.
Windows Server Update Services
By using Windows Server Update Services (WSUS), administrators can deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site.
Systems Management Server
The following table provides the SMS detection and deployment summary for this security update.
| Software | SMS 2.0 | SMS 2003 with SUSFP | SMS 2003 with ITMU | Configuration Manager 2007 |
|---|---|---|---|---|
| Microsoft Windows 2000 Service Pack 4 | Yes | Yes | Yes | Yes |
| Windows XP Professional Service Pack 2 and Windows XP Professional Service Pack 3 | Yes | Yes | Yes | Yes |
| Windows XP Professional x64 Edition Service Pack 2 | No | No | Yes | Yes |
| Windows Server 2003 Service Pack 2 | Yes | Yes | Yes | Yes |
| Windows Server 2003 x64 Edition Service Pack 2 | No | No | Yes | Yes |
| Windows Server 2003 with SP2 for Itanium-based Systems | No | No | Yes | Yes |
For SMS 2.0 and SMS 2003, the SMS SUS Feature Pack (SUSFP), which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. See also Downloads for Systems Management Server 2.0.
For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications. For more information about the Office Inventory Tool and other scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.
System Center Configuration Manager 2007 uses WSUS 3.0 for detection of updates. For more information about Configuration Manager 2007 Software Update Management, visit System Center Configuration Manager 2007.
For more information about SMS, visit the SMS Web site.
For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.
Update Compatibility Evaluator and Application Compatibility Toolkit
Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit 5.0.
The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.
Security Update Deployment
Affected Software
For information about the specific security update for your affected software, click the appropriate link:
Windows 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-KB970483-x86-ENU /quiet |
| Installing without restarting | Windows2000-KB970483-x86-ENU /norestart |
| Update log file | kb970483.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 Spuninst.exe utility located in the %Windir%\$NTUninstallKB970483$\Spuninst folder |
| File Information | See Microsoft Knowledge Base Article 970483 |
| Registry Key Verification | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB970483\Filelist |
Deployment Information
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about the installer, visit the Microsoft TechNet Web site.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed. |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Displays a dialog box prompting the local user to allow a restart. |
| Special Options | |
| /overwriteoem | Overwrites OEM files without prompting. |
| /nobackup | Does not back up files needed for uninstall. |
| /forceappsclose | Forces other programs to close when the computer shuts down. |
| /log:path | Allows the redirection of installation log files. |
| /extract[:path] | Extracts files without starting the Setup program. |
| /ER | Enables extended error reporting. |
| /verbose | Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Removing the Update
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed. |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Displays a dialog box prompting the local user to allow a restart. |
| Special Options | |
| /forceappsclose | Forces other programs to close when the computer shuts down. |
| /log:path | Allows the redirection of installation log files. |
Verifying That the Update Has Been Applied
- Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
- File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. - On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
- Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.
These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.
Windows XP Professional (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
| Deployment | |
| Installing without user intervention | For Windows XP Professional Service Pack 2 and Windows XP Professional Service Pack 3: Windowsxp-kb970483-x86-enu /quiet |
| For Windows XP Professional x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-kb970483-x64-enu /quiet | |
| Installing without restarting | For Windows XP Professional Service Pack 2 and Windows XP Professional Service Pack 3: Windowsxp-kb970483-x86-enu /norestart |
| For Windows XP Professional x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-kb970483-x64-enu /norestart | |
| Update log file | KB970483.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 Spuninst.exe utility located in the %Windir%\$NTUninstallKB970483$\Spuninst folder |
| File Information | See Microsoft Knowledge Base Article 970483 |
| Registry Key Verification | For all supported 32-bit editions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB970483\Filelist |
| For all supported x64-based editions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB970483\Filelist |
Note For supported versions of Windows XP Professional x64 Edition, this security update is the same as supported versions of the Windows Server 2003 x64 Edition security update.
Deployment Information
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about the installer, visit the Microsoft TechNet Web site.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed. |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Displays a dialog box prompting the local user to allow a restart. |
| Special Options | |
| /overwriteoem | Overwrites OEM files without prompting. |
| /nobackup | Does not back up files needed for uninstall. |
| /forceappsclose | Forces other programs to close when the computer shuts down. |
| /log:path | Allows the redirection of installation log files. |
| /integrate:path | Integrates the update into the Windows source files. These files are located at the path that is specified in the switch. |
| /extract[:path] | Extracts files without starting the Setup program. |
| /ER | Enables extended error reporting. |
| /verbose | Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Removing the Update
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Displays a dialog box prompting the local user to allow a restart. |
| Special Options | |
| /forceappsclose | Forces other programs to close when the computer shuts down. |
| /log:path | Allows the redirection of installation log files. |
Verifying That the Update Has Been Applied
- Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
- File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. - On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
- Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.
These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.
Windows Server 2003 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
| Deployment | |
| Installing without user intervention | For all supported 32-bit editions of Windows Server 2003: Windowsserver2003-kb970483-x86-enu /quiet |
| For all supported x64-based editions of Windows Server 2003: Windowsserver2003.WindowsXP-KB970483-x64-enu /quiet | |
| For all supported Itanium-based editions of Windows Server 2003: Windowsserver2003-KB970483-ia64-enu /quiet | |
| Installing without restarting | For all supported 32-bit editions of Windows Server 2003: Windowsserver2003-kb970483-x86-enu /norestart |
| For all supported x64-based editions of Windows Server 2003: Windowsserver2003.WindowsXP-KB970483-x64-enu /norestart | |
| For all supported Itanium-based editions of Windows Server 2003: Windowsserver2003-KB970483-ia64-enu /norestart | |
| Update log file | KB970483.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 | This security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341. |
| Removal Information | Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB970483$\Spuninst folder |
| File Information | See Microsoft Knowledge Base Article 970483 |
| Registry Key Verification | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB970483\Filelist |
Deployment Information
Installing the Update
When you install this security update, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about the installer, visit the Microsoft TechNet Web site.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed. |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Displays a dialog box prompting the local user to allow a restart. |
| Special Options | |
| /overwriteoem | Overwrites OEM files without prompting. |
| /nobackup | Does not back up files needed for uninstall. |
| /forceappsclose | Forces other programs to close when the computer shuts down. |
| /log:path | Allows the redirection of installation log files. |
| /integrate:path | Integrates the update into the Windows source files. These files are located at the path that is specified in the switch. |
| /extract[:path] | Extracts files without starting the Setup program. |
| /ER | Enables extended error reporting. |
| /verbose | Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Removing the Update
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed. |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Displays a dialog box prompting the local user to allow a restart. |
| Special Options | |
| /forceappsclose | Forces other programs to close when the computer shuts down. |
| /log:path | Allows the redirection of installation log files. |
Verifying that the Update Has Been Applied
- Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
- File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. - On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
- Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.
These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
- Yamata Li of Palo Alto Networks for reporting the IIS 5.0 WebDAV Authentication Bypass Vulnerability (CVE-2009-1122)
Microsoft Active Protections Program (MAPP)
To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please visit the active protections Web sites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.
Support
- Customers in the U.S. and Canada can receive technical support from Security Support or 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates. For more information about available support options, see Microsoft Help and Support.
- 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 (June 9, 2009): Bulletin published.
- V1.1 (June 17, 2009): Expanded on the "What causes the vulnerability?" FAQ entries for CVE-2009-1122 and CVE-2009-1535. This is an informational change only.