|
|
Microsoft Security Bulletin MS06-041
Vulnerability in DNS Resolution Could Allow Remote Code Execution (920683)
Published: August 8, 2006
Version: 1.0
Summary
Who Should Read this Document: Customers who use Microsoft Windows
Impact of Vulnerability: Remote Code Execution
Maximum Severity Rating: Critical
Recommendation: Customers should apply the update immediately
Security Update Replacement: None
Caveats: None
Tested Software and Security Update Download Locations:
Affected Software:
The software in this list has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.
Note The security updates for Microsoft Windows Server 2003, Windows Server 2003 Service Pack 1, and Windows Server 2003 x64 Edition also apply to Windows Server 2003 R2.
 |
|
Executive Summary:
This update resolves several newly discovered, privately reported, vulnerabilities.
An attacker who successfully exploited the most severe of these vulnerabilities could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
We recommend that customers apply this update immediately.
Severity Ratings and Vulnerability Identifiers:
Winsock Hostname Vulnerability - CVE-2006-3440 |
Remote Code Execution |
Critical |
Critical |
Critical |
Critical |
Critical |
DNS Client Buffer Overrun Vulnerability - CVE-2006-3441 |
Remote Code Execution
|
Critical |
Critical |
Critical |
Critical |
Critical |
Aggregate Severity of All Vulnerabilities |
|
Critical |
Critical |
Critical |
Critical |
Critical |
This assessment is based on the types of systems that are affected by the vulnerability, their typical deployment patterns, and the effect that exploiting the vulnerability would have on them.
Note The security updates for Windows Server 2003, Windows Server 2003 Service Pack 1, and Windows Server 2003 x64 Edition also apply to Windows Server 2003 R2.
Note The severity ratings for non-x86 operating system versions map to the x86 operating systems versions as follows:
| • |
The Windows XP Professional x64 Edition severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating. |
| • |
The Windows Server 2003 for Itanium-based Systems severity rating is the same as the Windows Server 2003 severity rating. |
| • |
The Windows Server 2003 with SP1 for Itanium-based Systems severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating. |
| • |
The Windows Server 2003 x64 Edition severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating. |
 |
|
Why does this update address several reported security vulnerabilities?
This update addresses 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 can install only this update.
Extended security update support for Microsoft Windows 98, Windows 98 Second Edition, or Windows Millennium Edition ended on July 11, 2006. I am still using one of these operating systems; what should I do?
Windows 98, Windows 98 Second Edition, and Windows Millennium Edition have reached the end of their support life cycles. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.
Extended security update support for Microsoft Windows NT Workstation 4.0 Service Pack 6a and Windows 2000 Service Pack 2 ended on June 30, 2004. Extended security update support for Microsoft Windows NT Server 4.0 Service Pack 6a ended on December 31, 2004. Extended security update support for Microsoft Windows 2000 Service Pack 3 ended on June 30, 2005. I am still using one of these operating systems; what should I do?
Windows NT Workstation 4.0 Service Pack 6a, Windows NT Server 4.0 Service Pack 6a, Windows 2000 Service Pack 2, and Windows 2000 Service Pack 3 have reached the end of their support life cycles. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.
Customers who require custom support for these products must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ.
For more information, visit the Windows Operating System FAQ.
Microsoft Windows 2000 Service Pack 4 |
Yes |
Yes |
Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2 |
Yes |
Yes |
Microsoft Windows XP Professional x64 Edition |
No |
Yes |
Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 |
Yes |
Yes |
Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with Service Pack 1 for Itanium-based Systems |
No |
Yes |
Microsoft Windows Server 2003 x64 Edition family |
No |
Yes |
For more information about MBSA, visit the MBSA Web site. For more information about the programs that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660.
For more detailed information, see Microsoft Knowledge Base Article 910723.
Can I use Systems Management Server (SMS) to determine whether this update is required?
The following table provides the SMS detection summary for this security update.
Microsoft Windows 2000 Service Pack 4 |
Yes |
Yes |
Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2 |
Yes |
Yes |
Microsoft Windows XP Professional x64 Edition |
No |
Yes |
Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 |
Yes |
Yes |
Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with Service Pack 1 for Itanium-based Systems |
No |
Yes |
Microsoft Windows Server 2003 x64 Edition family |
No |
Yes |
For more information about MBSA, visit the MBSA Web site. For more information about the programs that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660.
For more detailed information, see Microsoft Knowledge Base Article 910723.
|
|
|
|
|
|
There is a remote code execution vulnerability in Winsock that could allow an attacker who successfully exploited this vulnerability to take complete control of the affected system. For an attack to be successful the attacker would have to force the user to open a file or visit a website that is specially crafted to call the affected Winsock API.
| • |
The vulnerability could be exploited by an attacker who persuaded a user to open a specially crafted file or view a specially crafted website. There is no way for an attacker to force a user to open a specially crafted file, except potentially through previewing an e-mail message. |
|
|
|
Microsoft has tested the following workarounds. Although these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified in the following section.
| • |
Modify the Autodial DLL
Modifying the Autodial DLL within the Windows registry will prevent an application, specially crafted website or e-mail message from calling the affected API and exploiting the vulnerability. If the Autodial DLL registry value is not found by default in the specified location we recommend that customers create the REG_SZ value accordingly.
Note Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.
Note We recommend backing up the registry before you edit
| • |
Click Start, click Run, type "regedt32 " (without the quotation marks), and then click OK |
| • |
In Registry Editor, locate the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters |
| • |
Double click the REG_SZ value AutodialDLL |
| • |
Set the data value to kernel32.dll |
| • |
Close the regedt32 utility and reboot |
|
|
|
|
What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could remotely take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
What causes the vulnerability?
An unchecked buffer in the Winsock API.
What is Winsock?
Windows Sockets 2 (Winsock) enables programmers to create advanced Internet, intranet, and other network-capable applications to transmit application data across the wire, independent of the network protocol being used. With Winsock, programmers are provided access to advanced Microsoft® Windows® networking capabilities such as multicast and Quality of Service (QOS). For more information about Winsock, please see the following MSDN Article.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system.
How could an attacker exploit the vulnerability?
The vulnerability could be exploited by an attacker who persuaded a user to open a specially crafted file or view a specially crafted website. There is no way for an attacker to force a user to open a specially crafted file, except potentially through previewing an e-mail message. Additionally, if an application uses the affected API it is possible that it could be exploited during regular usage scenarios that may not require user action.
What systems are primarily at risk from the vulnerability?
Servers and workstations are primarily at risk from this vulnerability.
What does the update do?
The update removes the vulnerability by modifying the way that the affected function validates the message before it passes the message to the allocated buffer.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.
|
|
|
There is a remote code execution vulnerability in the DNS Client service that could allow an attacker who successfully exploited this vulnerability to take complete control of the affected system.
| • |
For an attack to be successful the attacker would either have to be on a subnet between the host and the DNS server or force the target host to make a DNS request to receive a specially crafted record response from an attacking server. |
Microsoft has tested the following workarounds. Although these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified in the following section.
| • |
For an attack to be successful the attackers would either have to be on a subnet between the host and the DNS server or force the target host to make a DNS request to receive a specially crafted record response from an attacking server. |
| • |
Block DNS related records at network gateways
Blocking the following DNS record types at network gateways will help protect the affected system from attempts to exploit this vulnerability.
| • |
ATMA |
| • |
TXT |
| • |
X25 |
| • |
HINFO |
| • |
ISDN DNS |
|
|
|
|
What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could remotely take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
What causes the vulnerability?
An unchecked buffer in the DNS client layer.
What is DNS?
The Domain Name System (DNS) client service resolves and caches DNS names. The DNS client service must be running on every computer that will perform DNS name resolution. The ability to resolve DNS names is crucial for locating domain controllers in Active Directory domains. The DNS client service is also critical for locating devices identified using DNS name resolution. For more information on the DNS client service please see the following Microsoft TechNet Article.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system.
How could an attacker exploit the vulnerability?
An anonymous user could exploit the vulnerability by sending a specially crafted DNS communication to an affected client. For an attack to be successful the attacker would either have to be on a subnet between the host and the DNS server or force the target host to make a DNS request to receive a specially crafted record response from an attacking server.
What systems are primarily at risk from the vulnerability?
Servers and workstations are primarily at risk from this vulnerability.
What does the update do?
The update removes the vulnerability by validating the way that the DNS client handles DNS related communications.
Could the vulnerability be exploited over the Internet?
An attacker could try to exploit this vulnerability over the Internet. Firewall best practices and standard default firewall configurations can help protect against attacks that originate from the Internet. Microsoft has provided information about how you can help protect your PC. End users can visit the Protect Your PC Web site. IT professionals can visit the Security Guidance Center Web site.
What does the update do?
The update removes the vulnerability by validating the way that the DNS client handles DNS related communications.
Would disabling the DNS client service or configuring the client to use a specific DNS server mitigate the vulnerability?
No. The vulnerability cannot be mitigated by disabling the DNS client service or configuring the use of a specific trusted DNS server.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.
|
|
|
Affected Software:
For information about the specific security update for your affected software, click the appropriate link:
|
|
|
Prerequisites
This security update requires Windows Server 2003 or Windows Server 2003 Service Pack 1.
Note The security updates for Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 also apply to Microsoft Windows Server 2003 R2.
Inclusion in Future Service Packs:
The update for this issue will be included in future Service Pack or Update Rollup.
Installation Information
This security update supports the following setup switches.
/help |
Displays the command-line options. |
/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. |
/norestart |
Does not restart when installation has completed. |
/forcerestart |
Restarts the computer after installation and forces other applications to close at shutdown without saving open files first. |
/warnrestart[:x] |
Displays a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
/promptrestart |
Display a dialog box prompting the local user to allow a restart. |
/overwriteoem |
Overwrites OEM files without prompting. |
/nobackup |
Does not back up files needed for uninstallation. |
/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. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.
Deployment Information
To install the security update without any user intervention, use the following command at a command prompt for Windows Server 2003:
Windowsserver2003-kb920683-x86-enu /quiet
Note Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB920683.log file for any failure messages when they use this switch.
To install the security update without forcing the system to restart, use the following command at a command prompt for Windows Server 2003:
Windowsserver2003-kb920683-x86-enu /norestart
For information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.
Restart Requirement
You must restart your system after you apply this security update.
This security update supports HotPatching. If you use HotPatching, you can install security updates on systems that are running Microsoft Windows Server 2003 Service Pack 1, without restarting the servers. For more information about HotPatching and how to deploy a security update by using HotPatching, see Microsoft Knowledge Base Article 897341.
The security update that is available on Windows Update, Microsoft, Update, and Automatic Update make use of HotPatching and will not require a restart of your server.
Note Not all security updates support HotPatching, and some security updates that support HotPatching might require that you restart the server after you install the security update. HotPatching is only supported if the files being replaced by the security update are General Distribution Release (GDR) files.
Removal Information
To remove this update, use the Add or Remove Programs tool in Control Panel.
System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB920683$\Spuninst folder.
/help |
Displays the command-line options. |
/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. |
/norestart |
Does not restart when installation has completed. |
/forcerestart |
Restarts the computer after installation and forces other applications to close at shutdown without saving open files first. |
/warnrestart[:x] |
Displays a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
/promptrestart |
Display a dialog box prompting the local user to allow a restart. |
/forceappsclose |
Forces other programs to close when the computer shuts down. |
/log:path |
Allows the redirection of installation log files. |
File Information
The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Datacenter Edition; Windows Server 2003, Enterprise Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; Windows Server 2003, Datacenter Edition with SP1; Windows Server 2003 R2, Web Edition; Windows Server 2003 R2, Standard Edition; Windows Server 2003 R2, Datacenter Edition; Windows Server 2003 R2, Enterprise Edition; Windows Small Business Server 2003 R2:
Dnsapi.dll |
5.2.3790.558 |
12-Jul-2006 |
18:44 |
151,040 |
x86 |
RTMGDR |
Rasadhlp.dll |
5.2.3790.558 |
12-Jul-2006 |
18:44 |
7,168 |
x86 |
RTMGDR |
Dnsapi.dll |
5.2.3790.558 |
12-Jul-2006 |
18:55 |
151,552 |
x86 |
RTMQFE |
Rasadhlp.dll |
5.2.3790.558 |
12-Jul-2006 |
18:55 |
7,168 |
x86 |
RTMQFE |
Dnsapi.dll |
5.2.3790.2745 |
12-Jul-2006 |
18:59 |
176,128 |
x86 |
SP1GDR |
Dnsapi.hp.dll |
5.2.3790.2745 |
12-Jul-2006 |
18:59 |
7,680 |
x86 |
SP1GDR |
Rasadhlp.dll |
5.2.3790.2745 |
12-Jul-2006 |
18:59 |
12,288 |
x86 |
SP1GDR |
Rasadhlp.hp.dll |
5.2.3790.2745 |
12-Jul-2006 |
18:59 |
4,096 |
x86 |
SP1GDR |
Dnsapi.dll |
5.2.3790.2745 |
12-Jul-2006 |
19:18 |
157,696 |
x86 |
SP1QFE |
Rasadhlp.dll |
5.2.3790.2745 |
12-Jul-2006 |
19:18 |
7,680 |
x86 |
SP1QFE |
Windows Server, 2003 Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; and Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems:
Dnsapi.dll |
5.2.3790.558 |
12-Jul-2006 |
19:43 |
414,208 |
IA-64 |
RTMGDR |
Rasadhlp.dll |
5.2.3790.558 |
12-Jul-2006 |
19:43 |
13,824 |
IA-64 |
RTMGDR |
Wdnsapi.dll |
5.2.3790.558 |
12-Jul-2006 |
19:43 |
151,040 |
x86 |
RTMGDR\WOW |
Wrasadhlp.dll |
5.2.3790.558 |
12-Jul-2006 |
19:43 |
7,168 |
x86 |
RTMGDR\WOW |
Dnsapi.dll |
5.2.3790.558 |
12-Jul-2006 |
19:44 |
416,768 |
IA-64 |
RTMQFE |
Rasadhlp.dll |
5.2.3790.558 |
12-Jul-2006 |
19:44 |
13,824 |
IA-64 |
RTMQFE |
Wdnsapi.dll |
5.2.3790.558 |
12-Jul-2006 |
19:44 |
151,552 |
x86 |
RTMQFE\WOW |
Wrasadhlp.dll |
5.2.3790.558 |
12-Jul-2006 |
19:44 |
7,168 |
x86 |
RTMQFE\WOW |
Dnsapi.dll |
5.2.3790.2745 |
12-Jul-2006 |
20:25 |
438,784 |
IA-64 |
SP1GDR |
Rasadhlp.dll |
5.2.3790.2745 |
12-Jul-2006 |
20:25 |
18,432 |
IA-64 |
SP1GDR |
Wdnsapi.dll |
5.2.3790.2745 |
12-Jul-2006 |
20:25 |
176,128 |
x86 |
SP1GDR\WOW |
Wrasadhlp.dll |
5.2.3790.2745 |
12-Jul-2006 |
20:25 |
12,288 |
x86 |
SP1GDR\WOW |
Dnsapi.dll |
5.2.3790.2745 |
12-Jul-2006 |
19:44 |
438,784 |
IA-64 |
SP1QFE |
Rasadhlp.dll |
5.2.3790.2745 |
12-Jul-2006 |
19:44 |
18,432 |
IA-64 |
SP1QFE |
Wdnsapi.dll |
5.2.3790.2745 |
12-Jul-2006 |
19:44 |
157,696 |
x86 |
SP1QFE\WOW |
Wrasadhlp.dll |
5.2.3790.2745 |
12-Jul-2006 |
19:44 |
7,680 |
x86 |
SP1QFE\WOW |
Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition; Windows Server 2003 R2, Standard x64 Edition; Windows Server 2003 R2, Enterprise x64 Edition; and Windows Server 2003 R2, Datacenter x64 Edition:
Dnsapi.dll |
5.2.3790.2745 |
12-Jul-2006 |
20:26 |
305,664 |
x64 |
SP1GDR |
Rasadhlp.dll |
5.2.3790.2745 |
12-Jul-2006 |
20:26 |
12,288 |
x64 |
SP1GDR |
Wdnsapi.dll |
5.2.3790.2745 |
12-Jul-2006 |
20:26 |
176,128 |
x86 |
SP1GDR\WOW |
Wrasadhlp.dll |
5.2.3790.2745 |
12-Jul-2006 |
20:26 |
12,288 |
x86 |
SP1GDR\WOW |
Dnsapi.dll |
5.2.3790.2745 |
12-Jul-2006 |
19:43 |
305,664 |
x64 |
SP1QFE |
Rasadhlp.dll |
5.2.3790.2745 |
12-Jul-2006 |
19:43 |
12,288 |
x64 |
SP1QFE |
Wdnsapi.dll |
5.2.3790.2745 |
12-Jul-2006 |
19:43 |
157,696 |
x86 |
SP1QFE\WOW |
Wrasadhlp.dll |
5.2.3790.2745 |
12-Jul-2006 |
19:43 |
7,680 |
x86 |
SP1QFE\WOW |
Notes When you install these security updates, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about the Update.exe installer, visit the Microsoft TechNet Web site.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
Verifying that the Update Has Been Applied
| • |
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site. |
| • |
File Version Verification
Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
1. |
Click Start, and then click Search. |
2. |
In the Search Results pane, click All files and folders under Search Companion. |
3. |
In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search. |
4. |
In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed. |
5. |
On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation. |
|
| • |
Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the following registry keys.
Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; Windows Server 2003, Datacenter Edition with SP1; Windows Server 2003, Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems; Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP2\KB920683\Filelist
Note This registry key may not contain a complete list of installed files. Also, this registry key may not be created correctly if an administrator or an OEM integrates or slipstreams the security update into the Windows installation source files. | |
INFORMATION BULLETIN
