Computer Security
[EN] securityvulns.ru no-pyccku


Related information

  Microsoft WordPad buffer overflow

  iDEFENSE Security Advisory 12.14.04 - Microsoft Word 6.0/95 Document Converter Buffer Overflow Vulnerability

From:MICROSOFT <secure_(at)_microsoft.com>
Date:15.12.2004
Subject:Microsoft Security Bulletin MS04-041 Vulnerability in WordPad Could Allow Code Execution (885836)

 Microsoft Security Bulletin MS04-041
 Vulnerability in WordPad Could Allow Code Execution (885836)
 
 Issued: December 14, 2004
 Version: 1.0
 
 Summary
 Who should read this document: Customers who use Microsoft Windows
 
 Impact of Vulnerability: Remote Code Execution
 
 Maximum Severity Rating: Important
 
 Recommendation: Customers should install the update at the earliest opportunity.
 
 Security Update Replacement: None
 
 Caveats: None
 
 Tested Software and Security Update Download Locations:
 
 Affected Software:
 
 • Microsoft Windows NT Server 4.0 Service Pack 6a – Download the update
 
 • Microsoft Windows NT Server 4.0 Terminal Server Edition Service Pack 6 – Download the update
 
 • Microsoft Windows 2000 Service Pack 3 and Microsoft Windows 2000 Service Pack 4 – Download the update
 
 • Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2 – Download the update
 
 • Microsoft Windows XP 64-Bit Edition Service Pack 1 – Download the update
 
 • Microsoft Windows XP 64-Bit Edition Version 2003 – Download the update
 
 • Microsoft Windows Server 2003 – Download the update
 
 • Microsoft Windows Server 2003 64-Bit Edition – Download the update
 
 • Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE), and Microsoft Windows Millennium Edition (ME) – Review the FAQ section of this bulletin for details about these operating systems.
 
 
 The software in this list has been tested to determine if the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support lifecycle for your product and version, visit the following Microsoft Support Lifecycle Web site.
 
 Top of section
 General Information
  Executive Summary
 
 Executive Summary:
 
 This update resolves several newly-discovered, privately reported vulnerabilities. Each vulnerability is documented in this bulletin in its own Vulnerability Details section.
 
 If a user is logged on with administrative privileges, an attacker who successfully exploited these vulnerabilities could take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts with full privileges. Users whose accounts are configured to have fewer privileges on the system would be at less risk than users who operate with administrative privileges. However, user interaction is required to exploit this vulnerability.
 
 We recommend that customers install the update at the earliest opportunity
 
 Severity Ratings and Vulnerability Identifiers:
 
 Vulnerability Identifiers Impact of Vulnerability Windows 98, 98 SE, ME Windows NT 4.0 Windows 2000 Windows XP Service Pack 1 Windows Server 2003 and Windows XP Service Pack 2
 Table Conversion Vulnerability - CAN-2004-0571
  Remote Code Execution
 
  Not Critical
  Important
  Important
  Important
  Moderate
 
 Font Conversion Vulnerability - CAN-2004-0901
  Remote Code Execution
 
  Not Critical
  Important
  Important
  Important
  Moderate
 
 Aggregate Severity of All Vulnerabilities
 
  Not Critical
  Important
  Important
  Important
  Moderate
 
 
 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.
 
 Top of section
  Frequently asked questions (FAQ) related to this security update
 
 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 can install only this update.
 
 Does this update contain any other security-related changes?
 Yes. Besides the changes that are listed in the Vulnerability Details section of this bulletin, this update includes the following change in functionality. We have made a defense in depth change that disables the Word for Windows 6.0 Converter by default. This change in functionality helps prevent future malicious use of the affected component. This change is consistent with the default settings in Windows XP Service Pack 2. Users who require this functionality can enable this converter by following the instructions that are documented in Microsoft Knowledge Based Article 870883. We do not recommend enabling this affected component unless this functionality is required.
 
 How does the extended support for Windows 98, Windows 98 Second Edition, and Windows Millennium Edition affect the release of security updates for these operating systems?
 Microsoft will only release security updates for critical security issues. Non-critical security issues are not offered during this support period. For more information about the Microsoft Support Lifecycle policies for these operating systems, visit the following Web site.
 
 Are Windows 98, Windows 98 Second Edition, or Windows Millennium Edition critically affected by any of the vulnerabilities that are addressed in this security bulletin?
 No. None of these vulnerabilities are critical in severity on Windows 98, on Windows 98 Second Edition, or on Windows Millennium Edition. For more information about severity ratings, visit the following Web site. For more information about severity ratings, visit the following Web site.
 
 I am still using Microsoft Windows NT 4.0 Workstation Service Pack 6a or Windows 2000 Service Pack 2, but extended security update support ended on June 30, 2004. What should I do?
 Windows NT 4.0 Workstation Service Pack 6a and Windows 2000 Service Pack 2 have reached the end of their life cycles as previously documented. Microsoft extended this support to June 30, 2004.
 
 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 Life Cycle, 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 following Microsoft Product Support Services Web site.
 
 Customers who require additional support for Windows NT Workstation 4.0 SP6a must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers who do not have 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.
 
 I am still using Windows XP, but extended security update support ended on September 30th, 2004. What should I do?
 
 The original version of Windows XP, generally known as Windows XP Gold or Windows XP Release to Manufacturing (RTM) version, reached the end of its extended security update support life cycle on September 30, 2004.
 
 It should be a priority for customers who have this operating system version to migrate to supported operating system versions to prevent potential exposure to vulnerabilities. For more information about the Windows Service Pack Product Life Cycle, visit the Microsoft Support Lifecycle Web site. For more information about the Windows Product Life Cycle, visit the Microsoft Support Lifecycle Web site.
 
 For more information, see the Windows Operating System Product Support Lifecycle FAQ.
 
 Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine if this update is required?
 Yes. MBSA will determine if this update is required. For more information about MBSA, visit the MBSA Web site.
 
 Note After April 20, 2004, the Mssecure.xml file that is used by MBSA 1.1.1 and earlier versions is no longer being updated with new security bulletin data. Therefore, scans that are performed after that date with MBSA 1.1.1 or earlier will be incomplete. All users should upgrade to MBSA 1.2 because it provides more accurate security update detection and supports additional products. Users can download MBSA 1.2.1 from the MBSA Web site. For more information about MBSA support, visit the following Microsoft Baseline Security Analyzer 1.2 Q&A Web site.
 
 Can I use Systems Management Server (SMS) to determine if this update is required?
 Yes. SMS can help detect and deploy this security update. For information about SMS, visit the SMS Web site.
 
 Top of section
  Vulnerability Details
 
  Table Conversion Vulnerability - CAN-2004-0571:
 
 A remote code execution vulnerability exists in the Microsoft Word for Windows 6.0 Converter. If a user is logged on with administrative privileges, an attacker who successfully exploited this vulnerability could take complete control of the affected system. However, user interaction is required to exploit this vulnerability.
 
  Mitigating Factors for Table Conversion Vulnerability - CAN-2004-0571:
 
 • In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site. After they click the link, they would be prompted to perform several actions. An attack could only occur after they performed these actions.
 
 • The vulnerability could not be exploited automatically through e-mail. For an attack to be successful a user must open an attachment that is sent in an e-mail message.
 
 • An attacker who successfully exploited this vulnerability could gain the same privileges as the user. Users whose accounts are configured to have fewer privileges on the system could be less impacted than users who operate with administrative privileges.
 
 • This vulnerability does not affect other Word documents, which are handled by separate converters.
 
 • Windows XP Service Pack 2 and Windows Server 2003 are at a reduced risk to this vulnerability because the affected component is disabled by default. These operating systems are only vulnerable if an administrator has manually enabled the affected component.
 
 • WordPad is vulnerable to this issue through .wri, .rtf, and .doc file name associations. By default, if any supported version of Microsoft Word is installed, through the .rtf and .doc file associations, these document types will open in Microsoft Word instead of WordPad. Microsoft Word does not contain this vulnerability. WordPad could also be used to manually open malicious documents; this could include files with file name extensions other than .wri, .rtf, and .doc because WordPad will process the malicious document the same regardless of the file name extension.
 
 
 Top of section
  Workarounds for Table Conversion Vulnerability - CAN-2004-0571:
 
 Microsoft has tested the following workarounds. While these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified below.
 
 • Do not open Word for Windows 6.0 documents using Microsoft WordPad.
 
 Do not open Word for Windows 6.0 documents from untrusted sources using any software listed as affected in this bulletin on systems that are not updated with the security updates that accompany this bulletin. This includes files that have .wri, .rtf, and .doc file associations. WordPad could also be used to manually open malicious documents; this could include files with file name extensions other than .wri, .rtf, and .doc because WordPad will process the malicious document the same regardless of the file name extension.
 
 • Use Microsoft Word to open the Word for Windows 6.0 document.
 
 This vulnerability is not present in any supported version of Microsoft Word. If Microsoft Word is installed, use that application to open the Word for Windows 6.0 document. This includes files that have .rtf and .doc file associations.
 
 • On Windows 2000 and Windows XP Service Pack 1, disable the handler for Word for Windows 6.0 converter:
 Deleting this registry key will help reduce attacks by preventing WordPad from processing Word for Windows 6.0 documents.
 
 Note Using Registry Editor incorrectly can cause serious problems that may require that 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 modify the registry, view the "Change 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 modify it.
 
 1.
  Click Start, click Run, type "regedt32" (without the quotation marks), and then click OK.
 
 2.
  In Registry Editor, locate the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Text Converters\Import\MSWord6.wpc
 
 3.
  Click on MSWord6.wpc and then press the Delete key on the keyboard.
 
 4.
  In the Confirm Key Delete dialog box, click OK.
 
 
 Impact of Workaround: WordPad will no longer be able to open Word for Windows 6.0 documents.
 
 • On Windows XP Service Pack 2 and Windows Server 2003, verify that the Word for Windows 6.0 converter has not been enabled:
 The Word for Windows 6.0 converter is not enabled by default on Windows XP Service Pack 2 and Windows Server 2003. If the instructions documented in Microsoft Knowledge Base Article 870883 have been followed to enable the Word for Windows 6.0 converter, it can be disabled. Deleting the following registry keys will help reduce attacks by preventing WordPad from processing Word for Windows 6.0 documents.
 
 Note Using Registry Editor incorrectly can cause serious problems that may require that 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 modify the registry, view the "Change 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 modify it.
 
 1.
  Click Start, click Run, type "regedt32" (without the quotation marks), and then click OK.
 
 2.
  In Registry Editor, locate the following registry keys:
 
 • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Applets\Wordpad\EnableLegacyConverters
 
 • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Applets\Wordpad\EnableLegacyConverters
 
 
 3.
  If they exist, click on each registry key and then press the Delete key on the keyboard.
 
 4.
  In the Confirm Key Delete dialog box, click OK.
 
 
 Impact of Workaround: WordPad will no longer be able to open Word for Windows 6.0 documents.
 
 • Delete or rename the Word for Windows 6.0 converter program file to another name.
 
 If WordPad cannot be removed using the methods documented in this section of the bulletin, to help prevent attack it may also be possible to delete or rename the physical file.
 
 Delete or rename the following files:
 
 • On Windows NT 4.0 Server:
 
 C:\Program Files\Windows NT\Accessories\mswd6_32.wpc
 
 • On Windows XP Service Pack 2:
 
 C:\Program Files\Windows NT\Accessories\mswrd6.wpc
 
 • On Windows 2000, Windows XP Service Pack 1, and Windows Server 2003:
 
 C:\Program Files\Common Files\Microsoft Shared\TextConv\MSWRD632.WPC
 
 
 Impact of Workaround: WordPad will no longer be able to open Word for Windows 6.0 documents.
 
 
 Top of section
  FAQ for Table Conversion Vulnerability - CAN-2004-0571:
 
 What is the scope of the vulnerability?
 This is a remote code execution vulnerability. If a user is logged on with administrative privileges, an attacker who successfully exploited this vulnerability could take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts with full privileges. Users whose accounts are configured to have fewer privileges on the system would be at less risk than users who operate with administrative privileges.
 
 What causes the vulnerability?
 An unchecked buffer in the Word for Windows 6.0 Converter.
 
 What is the Word for Windows 6.0 Converter?
 The Word for Windows 6.0 Converter helps users convert documents from Word 6.0 formats to the WordPad file format. The Word for Windows 6.0 Converter is included on all affected operating systems. However, user interaction is required to exploit this vulnerability.
 
 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 attacker could exploit the vulnerability by sending a malicious file to the user and by persuading the user to open the file. If the user opened the file, WordPad could fail and could allow the attacker to execute arbitrary code. This includes files that have .wri, .rtf, and .doc file associations. WordPad could also be used to manually open malicious documents; this could include files with file name extensions other than .wri, .rtf, and .doc because WordPad will process the malicious document the same regardless of the file name extension.
 
 In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site. After they click the link, they would be prompted to perform several actions. An attack could only occur after they performed these actions, such as opening a malicious file after being prompted by Internet Explorer.
 
 Can the vulnerability be exploited automatically through an e-mail message?
 No. A user must open a malicious document that an attacker provided in order for the vulnerability to be exploited. Viewing an e-mail message, even if Microsoft Word had been selected as the default e-mail editor for Microsoft Outlook, would not expose the vulnerability.
 
 What systems are primarily at risk from the vulnerability?
 Workstations and terminal servers are primarily at risk.
 
 How are Windows XP Service Pack 2 and Windows Server 2003 affected by this vulnerability?
 The Word for Windows 6.0 converter is not enabled by default on Windows XP Service Pack 2 and Windows Server 2003. If the instructions documented in Microsoft Knowledge Base Article 870883 have been followed to enable the Word for Windows 6.0 converter, it can be disabled. See the Workaround section for details on disabling the Word for Windows 6.0 converter if it has been enabled.
 
 Are Windows 98, Windows 98 Second Edition or Windows Millennium Edition critically affected by this vulnerability?
 No. Although Windows 98, Windows 98 Second Edition, and Windows Millennium Edition do contain the affected component, the vulnerability is not critical. For more information about severity ratings, visit the following Web site.
 
 What does the update do?
 The update removes the vulnerability by modifying the way that the Word for Windows 6.0 Converter validates the length of a 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. Microsoft had not received any information indicating 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 indicating 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.
 
 Top of section
 Top of section
  Font Conversion Vulnerability - CAN-2004-0901:
 
 A remote code execution vulnerability exists in the Microsoft Word for Windows 6.0 Converter. If a user is logged on with administrative privileges, an attacker who successfully exploited this vulnerability could take complete control of the affected system. However, user interaction is required to exploit this vulnerability.
 
  Mitigating Factors for Font Conversion Vulnerability - CAN-2004-0901:
 
 • In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site. After they click the link, they would be prompted to perform several actions. An attack could only occur after they performed these actions.
 
 • The vulnerability could not be exploited automatically through e-mail. For an attack to be successful a user must open an attachment that is sent in an e-mail message.
 
 • An attacker who successfully exploited this vulnerability could gain the same privileges as the user. Users whose accounts are configured to have fewer privileges on the system could be less impacted than users who operate with administrative privileges.
 
 • This vulnerability does not affect other Word documents, which are handled by separate converters.
 
 • Windows XP Service Pack 2 and Windows Server 2003 are at a reduced risk to this vulnerability because the affected component is disabled by default. These operating systems are only vulnerable if an administrator has manually enabled the affected component.
 
 • WordPad is vulnerable to this issue through .wri, .rtf, and .doc file name associations. By default, if any supported version of Microsoft Word is installed, through the .rtf and .doc file associations, these document types will open in Microsoft Word instead of WordPad. Microsoft Word does not contain this vulnerability. WordPad could also be used to manually open malicious documents; this could include files with file name extensions other than .wri, .rtf, and .doc because WordPad will process the malicious document the same regardless of the file name extension.
 
 
 Top of section
  Workarounds for Font Conversion Vulnerability - CAN-2004-0571:
 
 Microsoft has tested the following workarounds. While these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified below.
 
 • Do not open Word for Windows 6.0 documents using Microsoft WordPad.
 
 Do not open Word for Windows 6.0 documents from untrusted sources using any software listed as affected in this bulletin on systems that are not updated with the security updates that accompany this bulletin. This includes files that have .wri, .rtf, and .doc file associations. WordPad could also be used to manually open malicious documents; this could include files with file name extensions other than .wri, .rtf, and .doc because WordPad will process the malicious document the same regardless of the file name extension.
 
 • Use Microsoft Word to open the Word for Windows 6.0 document.
 
 This vulnerability is not present in any supported version of Microsoft Word. If Microsoft Word is installed, use that application to open the Word for Windows 6.0 document. This includes files that have .rtf and .doc file associations.
 
 • On Windows 2000 and Windows XP Service Pack 1, disable the handler for Word for Windows 6.0 converter:
 Deleting this registry key will help reduce attacks by preventing WordPad from processing Word for Windows 6.0 documents.
 
 Note Using Registry Editor incorrectly can cause serious problems that may require that 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 modify the registry, view the "Change 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 modify it.
 
 1.
  Click Start, click Run, type "regedt32" (without the quotation marks), and then click OK.
 
 2.
  In Registry Editor, locate the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Text Converters\Import\MSWord6.wpc
 
 3.
  Click on MSWord6.wpc and then press the Delete key on the keyboard.
 
 4.
  In the Confirm Key Delete dialog box, click OK.
 
 
 Impact of Workaround: WordPad will no longer be able to open Word for Windows 6.0 documents.
 
 • On Windows XP Service Pack 2 and Windows Server 2003, verify that the Word for Windows 6.0 converter has not been enabled:
 The Word for Windows 6.0 converter is not enabled by default on Windows XP Service Pack 2 and Windows Server 2003. If the instructions documented in Microsoft Knowledge Base Article 870883 have been followed to enable the Word for Windows 6.0 converter, it can be disabled. Deleting the following registry keys will help reduce attacks by preventing WordPad from processing Word for Windows 6.0 documents.
 
 Note Using Registry Editor incorrectly can cause serious problems that may require that 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 modify the registry, view the "Change 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 modify it.
 
 1.
  Click Start, click Run, type "regedt32" (without the quotation marks), and then click OK.
 
 2.
  In Registry Editor, locate the following registry keys:
 
 • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Applets\Wordpad\EnableLegacyConverters
 
 • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Applets\Wordpad\EnableLegacyConverters
 
 
 3.
  If they exist, click on each registry key and then press the Delete key on the keyboard.
 
 4.
  In the Confirm Key Delete dialog box, click OK.
 
 
 Impact of Workaround: WordPad will no longer be able to open Word for Windows 6.0 documents.
 
 • Delete or rename the Word for Windows 6.0 converter program file to another name.
 
 If WordPad cannot be removed using the methods documented in this section of the bulletin, to help prevent attack it may also be possible to delete or rename the physical file.
 
 Delete or rename the following files:
 
 • On Windows NT 4.0 Server:
 
 C:\Program Files\Windows NT\Accessories\mswd6_32.wpc
 
 • On Windows XP Service Pack 2:
 
 C:\Program Files\Windows NT\Accessories\mswrd6.wpc
 
 • On Windows 2000, Windows XP Service Pack 1, and Windows Server 2003:
 
 C:\Program Files\Common Files\Microsoft Shared\TextConv\MSWRD632.WPC
 
 
 Impact of Workaround: WordPad will no longer be able to open Word for Windows 6.0 documents.
 
 
 Top of section
  FAQ for Font Conversion Vulnerability - CAN-2004-0901:
 
 What is the scope of the vulnerability?
 This is a remote code execution vulnerability. If a user is logged on with administrative privileges, an attacker who successfully exploited this vulnerability could take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts with full privileges. Users whose accounts are configured to have fewer privileges on the system would be at less risk than users who operate with administrative privileges.
 
 What causes the vulnerability?
 An unchecked buffer in the Word for Windows 6.0 Converter.
 
 What is the Word for Windows 6.0 Converter?
 The Word for Windows 6.0 Converter helps users convert documents from Word 6.0 formats to the WordPad file format. The Word for Windows 6.0 Converter is included on all affected operating systems. However, user interaction is required to exploit this vulnerability.
 
 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 attacker could exploit the vulnerability by sending a malicious file to the user and by persuading the user to open the file. If the user opened the file, WordPad could fail and could allow the attacker to execute arbitrary code. This includes files that have .wri, .rtf, and .doc file associations. WordPad could also be used to manually open malicious documents; this could include files with file name extensions other than .wri, .rtf, and .doc because WordPad will process the malicious document the same regardless of the file name extension.
 
 In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site. After they click the link, they would be prompted to perform several actions. An attack could only occur after they performed these actions, such as opening a malicious file after being prompted by Internet Explorer.
 
 Can the vulnerability be exploited automatically through an e-mail message?
 No. A user must open a malicious document that an attacker provided in order for the vulnerability to be exploited. Viewing an e-mail message, even if Microsoft Word had been selected as the default e-mail editor for Microsoft Outlook, would not expose the vulnerability.
 
 What systems are primarily at risk from the vulnerability?
 Workstations and terminal servers are primarily at risk.
 
 How are Windows XP Service Pack 2 and Windows Server 2003 affected by this vulnerability?
 The Word for Windows 6.0 converter is not enabled by default on Windows XP Service Pack 2 and Windows Server 2003. If the instructions documented in Microsoft Knowledge Base Article 870883 have been followed to enable the Word for Windows 6.0 converter, it can be disabled. See the Workaround section for details on disabling the Word for Windows 6.0 converter if it has been enabled.
 
 Are Windows 98, Windows 98 Second Edition or Windows Millennium Edition critically affected by this vulnerability?
 No. Although Windows 98, Windows 98 Second Edition, and Windows Millennium Edition do contain the affected component, the vulnerability is not critical. For more information about severity ratings, visit the following Web site.
 
 What does the update do?
 The update removes the vulnerability by modifying the way that the Word for Windows 6.0 Converter validates the length of a 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. Microsoft had not received any information indicating 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 indicating 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.
 
 Top of section
 Top of section
 Top of section
  Security Update Information
 
 Installation Platforms and Prerequisites:
 
 For information about the specific security update for your platform, click the appropriate link:
 
  Windows Server 2003 (all versions)
 
 Prerequisites
 This security update requires a release version of Windows Server 2003.
 
 Inclusion in Future Service Packs:
 The update for this issue will be included in Windows Server 2003 Service Pack 1.
 
 Installation Information
 
 This security update supports the following setup switches:
 
  /help Displays the command line options
 
 Setup Modes
 
  /quiet Quiet mode (no user interaction or display)
 
  /passive Unattended mode (progress bar only)
 
  /uninstall Uninstalls the package
 
 Restart Options
 
  /norestart Do not restart when installation is complete
 
  /forcerestart Restart after installation
 
 Special Options
 
  /l Lists installed Windows hotfixes or update packages
 
  /o Overwrite OEM files without prompting
 
  /n Do not backup files needed for uninstall
 
  /f Force other programs to close when the computer shuts down
 
  /integrate:path Integrates the update into the Windows source files located at the path specified.
 
  /extract Extracts files without starting setup
 
 Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the previous version of the setup utility 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-kb885836-x86-enu /passive /quiet
 
 To install the security update without forcing the system to restart, use the following command at a command prompt for Windows Server 2003:
 
 Windowsserver2003-kb885836-x86-enu /norestart
 
 For information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site.
 
 Restart Requirement
 
 This update does not require a restart. If the required files are in use, this update will require a restart. If this occurs, a message appears that advises you to restart.
 
 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%\$NTUninstallKB885836$\Spuninst folder. The Spuninst.exe utility supports the following setup switches:
 
  /help Displays the command line options
 
 Setup Modes
 
  /quiet Quiet mode (no user interaction or display)
 
  /passive Unattended mode (progress bar only)
 
 Restart Options
 
  /norestart Do not restart when installation is complete
 
  /forcerestart Restart after installation
 
 Special Options
 
  /f Force other programs to close when the computer shuts down
 
 File Information
 
 The English version of this update has the file attributes (or later) 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 Enterprise Edition, Windows Server 2003 Standard Edition, Windows Server 2003 Web Edition, and Windows Server 2003 Datacenter Edition:
 
 File Name Version Date Time Size Folder
 Mswrd632.wpc
  2004.10.25.0
  26-Oct-2004
  17:38
  181,248
  RTMGDR
 
 Wordpad.exe
  5.2.3790.224
  19-Oct-2004
  00:35
  201,728
  RTMGDR
 
 Mswrd632.wpc
  2004.10.25.0
  26-Oct-2004
  17:33
  181,248
  RTMQFE
 
 Wordpad.exe
  5.2.3790.224
  19-Oct-2004
  00:34
  201,728
  RTMQFE
 
 
 Windows Server 2003 64-Bit Enterprise Edition and Windows Server 2003 64-Bit Datacenter Edition:
 
 File Name Version Date Time Size CPU Folder
 Mswrd664.wpc
  2004.10.25.0
  26-Oct-2004
  17:39
  455,168
 
  RTMGDR
 
 Wordpad.exe
  5.2.3790.224
  19-Oct-2004
  00:35
  578,560
  IA-64
  RTMGDR
 
 Wmswrd632.wpc
  2004.10.25.0
  26-Oct-2004
  17:38
  181,248
 
  RTMGDR\WOW
 
 Wwordpad.exe
  5.2.3790.224
  19-Oct-2004
  00:35
  201,728
  x86
  RTMGDR\WOW
 
 Mswrd664.wpc
  2004.10.25.0
  26-Oct-2004
  17:31
  455,168
 
  RTMQFE
 
 Wordpad.exe
  5.2.3790.224
  19-Oct-2004
  00:35
  578,560
  IA-64
  RTMQFE
 
 Wmswrd632.wpc
  2004.10.25.0
  26-Oct-2004
  17:33
  181,248
 
  RTMQFE\WOW
 
 Wwordpad.exe
  5.2.3790.224
  19-Oct-2004
  00:34
  201,728
  x86
  RTMQFE\WOW
 
 
 Note When you install this security update on Windows Server 2003, the installer checks to see if any 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 an affected file, the installer copies the RTMQFE files to your system. Otherwise, the installer copies the RTMGDR files to your system.
 
 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 Update Installation
 
 • Microsoft Baseline Security Analyzer
 
 To verify that a security update is installed on an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. This tool 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 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 the update installation. 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.
 
 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP1\KB885836\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 885836 security update into the Windows installation source files.
 
 
 Top of section
 
  Windows XP (all versions)
 
 Note For Windows XP 64-Bit Edition Version 2003, this security update is the same as the Windows Server 2003 64-Bit Edition security update.
 
 Prerequisites
 This security update requires the release version Windows XP Service Pack 1 (SP1) or Windows XP Service Pack 2. For more information, see Microsoft Knowledge Base Article 322389.
 
 Inclusion in Future Service Packs:
 The update for this issue will be included in Windows XP Service Pack 3.
 
 Installation Information
 
 This security update supports the following setup switches:
 
  /help Displays the command line options
 
 Setup Modes
 
  /quiet Quiet mode (no user interaction or display)
 
  /passive Unattended mode (progress bar only)
 
  /uninstall Uninstalls the package
 
 Restart Options
 
  /norestart Do not restart when installation is complete
 
  /forcerestart Restart after installation
 
 Special Options
 
  /l Lists installed Windows hotfixes or update packages
 
  /o Overwrite OEM files without prompting
 
  /n Do not backup files needed for uninstall
 
  /f Force other programs to close when the computer shuts down
 
  /integrate:path Integrates the update into the Windows source files located at the path specified.
 
  /extract Extracts files without starting setup
 
 Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the previous version of the setup utility 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 XP:
 
 Windowsxp-kb885836-x86-enu /passive /quiet
 
 To install the security update without forcing the system to restart, use the following command at a command prompt for Windows XP:
 
 Windowsxp-kb885836-x86-enu /norestart
 
 For more information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site.
 
 Restart Requirement
 
 This update does not require a restart. If the required files are in use, this update will require a restart. If this occurs, a message appears that advises you to restart.
 
 Removal Information
 
 To remove this security update, use the Add or Remove Programs tool in Control Panel.
 
 System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe is located in the %Windir%\$NTUninstallKB885836$\Spuninst folder. The Spuninst.exe utility supports the following setup switches:
 
  /help Displays the command line options
 
 Setup Modes
 
  /quiet Quiet mode (no user interaction or display)
 
  /passive Unattended mode (progress bar only)
 
 Restart Options
 
  /norestart Do not restart when installation is complete
 
  /forcerestart Restart after installation
 
 Special Options
 
  /f Force other programs to close when the computer shuts down
 
 File Information
 
 The English version of this update has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
 
 Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:
 
 File Name Version Date Time Size Folder
 Mswrd632.wpc
  2004.10.25.0
  26-Oct-2004
  00:48
  181,248
  SP1QFE
 
 Wordpad.exe
  5.1.2600.1606
  28-Oct-2004
  18:06
  201,216
  SP1QFE
 
 Mswrd6.wpc
  10.0.803.2
  19-Oct-2004
  22:49
  186,880
  SP2GDR
 
 Mswrd6.wpc
  10.0.803.2
  19-Oct-2004
  22:36
  186,880
  SP2QFE
 
 
 Windows XP 64-Bit Edition Service Pack 1:
 
 File Name Version Date Time Size CPU Folder
 Mswrd664.wpc
  2004.10.25.0
  26-Oct-2004
  18:02
  455,168
 
  SP1QFE
 
 Wordpad.exe
  5.1.2600.1606
  28-Oct-2004
  18:10
  581,120
  IA-64
  SP1QFE
 
 Wmswrd632.wpc
  2004.10.25.0
  26-Oct-2004
  00:48
  181,248
 
  SP1QFE\WOW
 
 Wwordpad.exe
  5.1.2600.1606
  28-Oct-2004
  18:06
  201,216
  x86
  SP1QFE\WOW
 
 
 Windows XP 64-Bit Edition Version 2003:
 
 File Name Version Date Time Size CPU Folder
 Mswrd664.wpc
  2004.10.25.0
  26-Oct-2004
  17:39
  455,168
 
  RTMGDR
 
 Wordpad.exe
  5.2.3790.224
  19-Oct-2004
  00:35
  578,560
  IA-64
  RTMGDR
 
 Wmswrd632.wpc
  2004.10.25.0
  26-Oct-2004
  17:38
  181,248
 
  RTMGDR\WOW
 
 Wwordpad.exe
  5.2.3790.224
  19-Oct-2004
  00:35
  201,728
  x86
  RTMGDR\WOW
 
 Mswrd664.wpc
  2004.10.25.0
  26-Oct-2004
  17:31
  455,168
 
  RTMQFE
 
 Wordpad.exe
  5.2.3790.224
  19-Oct-2004
  00:35
  578,560
  IA-64
  RTMQFE
 
 Wmswrd632.wpc
  2004.10.25.0
  26-Oct-2004
  17:33
  181,248
 
  RTMQFE\WOW
 
 Wwordpad.exe
  5.2.3790.224
  19-Oct-2004
  00:34
  201,728
  x86
  RTMQFE\WOW
 
 
 Notes The Windows XP and Windows XP 64-Bit Edition Version 2003 versions of this security update are packaged as dual-mode packages. These dual-mode packages contain files for the original version of Windows XP Service Pack 1 (SP1) and files for Windows XP Service Pack 2 (SP2).
 
 For more information about dual-mode packages, see Microsoft Knowledge Base Article 328848.
 
 When you install this security update on Windows XP SP2 or on Windows XP 64-Bit Edition Version 2003, 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 an affected file, one of the following conditions occurs, depending on your operating system:
 
 • Windows XP SP2
 
 The installer copies the SP2QFE files to your system.
 
 • Windows XP 64-Bit Edition Version 2003
 
 The installer copies the RTMQFE files to your system.
 
 
 If you have not previously installed a hotfix to update an affected file, one of the following conditions occurs, depending on your operating system:
 
 • Windows XP SP2
 
 The installer copies the SP2GDR files to your system.
 
 • Windows XP 64-Bit Edition Version 2003
 
 The installer copies the RTMGDR files to your system.
 
 
 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 Update Installation
 
 • Microsoft Baseline Security Analyzer
 
 To verify that a security update is installed on an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. This tool 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 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 the update installation. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
 
 
 • Registry Key Verification
 
 You may also be able to verify the files that this security update has installed by reviewing the following registry keys.
 
 For Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:
 
 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB885836\Filelist
 
 For Windows XP 64-Bit Edition Version 2003:
 
 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP1\KB885836\Filelist
 
 Note These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly if an administrator or an OEM integrates or slipstreams the 885836 security update into the Windows installation source files.
 
 
 Top of section
 
  Windows 2000 (all versions)
 
 Prerequisites
 For Windows 2000, this security update requires Service Pack 3 (SP3) or Service Pack 4 (SP4).
 
 The software that is listed has been tested to determine if the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support lifecycle for your product and version, visit the Microsoft Support Lifecycle Web site.
 
 For more information about how to obtain the latest service pack, see Microsoft Knowledge Base Article 260910.
 
 Inclusion in Future Service Packs:
 The update for this issue will be included in a future Update Rollup.
 
 Installation Information
 
 This security update supports the following setup switches:
 
  /help Displays the command line options
 
 Setup Modes
 
  /quiet Quiet mode (no user interaction or display)
 
  /passive Unattended mode (progress bar only)
 
  /uninstall Uninstalls the package
 
 Restart Options
 
  /norestart Do not restart when installation is complete
 
  /forcerestart Restart after installation
 
 Special Options
 
  /l Lists installed Windows hotfixes or update packages
 
  /o Overwrite OEM files without prompting
 
  /n Do not backup files needed for uninstall
 
  /f Force other programs to close when the computer shuts down
 
  /integrate:path Integrates the update into the Windows source files located at the path specified.
 
  /extract Extracts files without starting setup
 
 Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the previous version of the setup utility uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
 
 Deployment Information
 
 To install the security update without any user intervention, use the following command at a command prompt for Windows 2000 Service Pack 3 and Windows 2000 Service Pack 4:
 
 Windows2000-kb885836-x86-enu /passive /quiet
 
 To install the security update without forcing the system to restart, use the following command at a command prompt for Windows 2000 Service Pack 3 and Windows 2000 Service Pack 4:
 
 Windows2000-kb885836-x86-enu /norestart
 
 For more information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site.
 
 Restart Requirement
 
 This update does not require a restart. If the required files are in use, this update will require a restart. If this occurs, a message appears that advises you to restart.
 
 Removal Information
 
 To remove this security update, use the Add or Remove Programs tool in Control Panel.
 
 System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB885836$\Spuninst folder. The Spuninst.exe utility supports the following setup switches:
 
  /help Displays the command line options
 
 Setup Modes
 
  /quiet Quiet mode (no user interaction or display)
 
  /passive Unattended mode (progress bar only)
 
 Restart Options
 
  /norestart Do not restart when installation is complete
 
  /forcerestart Restart after installation
 
 Special Options
 
  /f Force other programs to close when the computer shuts down
 
 File Information
 
 The English version of this update has the file attributes (or later) 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.
 
 Note Date, time, file name, or size information could change during installation. See the Verifying Update Installation section for details about how to verify an installation.
 
 Windows 2000 Service Pack 3 and Windows 2000 Service Pack 4:
 
 File Name Version Date Time Size
 Mswrd632.wpc
  2004.10.21.0
  25-Oct-2004
  09:10
  181,248
 
 Wordpad.exe
  5.0.2195.6991
  20-Oct-2004
  10:54
  185,616
 
 
 Verifying Update Installation
 
 • Microsoft Baseline Security Analyzer
 
 To verify that a security update is installed on an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. This tool 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 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 the update installation. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
 
 
 • Registry Key Verification
 
 You may also be able to verify the files that this security update has installed by reviewing the following registry key:
 
 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB885836\Filelist
 
 Note This registry key may not contain a complete list of installed files. Also, this registry key may not be created correctly when an administrator or an OEM integrates or slipstreams the 885836 security update into the Windows installation source files.
 
 
 Top of section
 
  Windows NT 4.0 (all versions)
 
 Prerequisites
 This security update requires Windows NT Server 4.0 Service Pack 6a (SP6a) or Windows NT Server 4.0 Terminal Server Edition Service Pack 6 (SP6).
 
 The software that is listed has been tested to determine if the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support lifecycle for your product and version, visit the following Microsoft Support Lifecycle Web site.
 
 For more information about obtaining the latest service pack, see Microsoft Knowledge Base Article 152734.
 
 Installation Information
 
 This security update supports the following setup switches:
 
  /y: Perform removal (only with /m or /q )
 
  /f: Force programs to quit during the shutdown process
 
  /n: Do not create an Uninstall folder
 
  /z: Do not restart when the update completes
 
  /q: Use Quiet or Unattended mode with no user interface (this switch is a superset of /m )
 
  /m: Use Unattended mode with a user interface
 
  /l: List the installed hotfixes
 
  /x: Extract the files without running Setup
 
 Note You can combine these switches into one command. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
 
 Deployment Information
 
 To install the security update without any user intervention, use the following command at a command prompt for Windows NT Server 4.0:
 
 Windowsnt4server-kb885836-x86-enu /q
 
 For Windows NT Server 4.0 Terminal Server Edition:
 
 Windowsnt4terminalserver-kb885836-x86-enu /q
 
 To install the security update without forcing the system to restart, use the following command at a command prompt for Windows NT Server 4.0:
 
 Windowsnt4server-kb885836-x86-enu /z
 
 For Windows NT Server 4.0 Terminal Server Edition:
 
 Windowsnt4terminalserver-kb885836-x86-enu /z
 
 For more information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site.
 
 Restart Requirement
 
 You must restart your computer after you apply this security update.
 
 Removal Information
 
 To remove this security update, use the Add/Remove Programs tool in Control Panel.
 
 System administrators can also use the Hotfix.exe utility to remove this security update. The Hotfix.exe utility is located in the %Windir%\$NTUninstallKB885836$ folder. The Hotfix.exe utility supports the following setup switches:
 
 /y: Perform removal (only with the /m or /q switch)
 
 /f: Force programs to quit during the shutdown process
 
 /n: Do not create an Uninstall folder
 
 /z: Do not restart when the installation is complete
 
 /q: Use Quiet or Unattended mode with no user interface (this switch is a superset of the /m switch)
 
 /m: Use Unattended mode with a user interface
 
 /l: List the installed hotfixes
 
 File Information
 
 The English version of this update has the file attributes (or later) 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.
 
 Note Date, time, file name, or size information could change during installation. See the Verifying Update Installation section for details about how to verify an installation.
 
 Windows NT Server 4.0:
 
 File Name Version Date Time Size
 Mswd6_32.wpc
  2004.10.21.0
  25-Oct-2004
  08:46
  181,248
 
 Wordpad.exe
  4.0.1381.7312
  25-Oct-2004
  08:49
  205,072
 
 
 Windows NT Server 4.0 Terminal Server Edition:
 
 File Name Version Date Time Size
 Mswd6_32.wpc
  2004.10.21.0
  25-Oct-2004
  09:00
  181,248
 
 Wordpad.exe
  4.0.1381.33598
  25-Oct-2004
  09:03
  205,584
 
 
 Verifying Update Installation
 
 • Microsoft Baseline Security Analyzer
 
 To verify that a security update is installed on an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. This tool 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 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 the update installation. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
 
 
 • Registry Key Verification
 
 You may also be able to verify the files that this security update has installed by reviewing the following registry key:
 
 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB885836\File 1
 
 Note This registry key may not contain a complete list of installed files. Also, this registry key may not be created correctly when an administrator or an OEM integrates or slipstreams the 885836 security update into the Windows installation source files.
 
 
 Top of section
 
 
 Top of section
 Acknowledgments
 
 Microsoft thanks the following for working with us to help protect customers:
 
 • Greg Jones of KPMG UK for reporting the Table Conversion Vulnerability (CAN-2004-0571).
 
 • Lord Yup working with iDefense for reporting the Font Conversion Vulnerability (CAN-2004-0901).
 
 
 Obtaining Other Security Updates:
 
 Updates for other security issues are available from the following locations:
 
 • Security updates are available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch."
 
 • Updates for consumer platforms are available from the Windows Update Web site.
 
 
 Support:
 
 • Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.
 
 • International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.
 
 
 Security Resources:
 
 • The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.
 
 • Microsoft Software Update Services
 
 • Microsoft Baseline Security Analyzer (MBSA)
 
 • Windows Update
 
 • Windows Update Catalog: For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166.
 
 • Office Update
 
 
 Software Update Services:
 
 By using Microsoft Software Update Services (SUS), administrators can quickly and reliably deploy the latest critical updates and security updates to Windows 2000 and Windows Server 2003-based servers, and to desktop systems that are running Windows 2000 Professional or Windows XP Professional.
 
 For more information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site.
 
 Systems Management Server:
 
 Microsoft Systems Management Server (SMS) delivers a highly-configurable enterprise solution for managing updates. By using SMS, administrators can identify Windows-based systems that require security updates and to perform controlled deployment of these updates throughout the enterprise with minimal disruption to end users. For more information about how administrators can use SMS 2003 to deploy security updates, visit the SMS 2003 Security Patch Management Web site. SMS 2.0 users can also use Software Updates Service Feature Pack to help deploy security updates. For information about SMS, visit the SMS Web site.
 
 Note SMS uses the Microsoft Baseline Security Analyzer and the Microsoft Office Detection Tool to provide broad support for security bulletin update detection and deployment. Some software updates may not be detected by these tools. Administrators can use the inventory capabilities of the SMS in these cases to target updates to specific systems. For more information about this procedure, see the following Web site. Some security updates require administrative rights following a restart of the system. Administrators can use the Elevated Rights Deployment Tool (available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 Administration Feature Pack) to install these updates.
 
 Disclaimer:
 
 The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
 
 Revisions:
 
 • V1.0 (December 14, 2004): Bulletin published
 
 

About | Terms of use | Privacy Policy
© SecurityVulns, 3APA3A, Vladimir Dubrovin
Nizhny Novgorod