Export (0) Print
Expand All

Microsoft Security Bulletin MS04-043 - Important

Vulnerability in HyperTerminal Could Allow Code Execution (873339)

Published: December 14, 2004

Version: 1.0

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:

Non-Affected Software:

  • Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE), and Microsoft Windows Millennium Edition (ME)

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.

General Information

Executive Summary:

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

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. 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 IdentifiersImpact of VulnerabilityWindows NT 4.0Windows 2000Windows XPWindows Server 2003
HyperTerminal Vulnerability - CAN-2004-0568Remote Code ExecutionImportantImportantImportantModerate

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.

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 phone numbers. When you call, ask to speak with the local Premier Support sales manager.

For more information, see the Windows Operating System 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, commonly 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, visit the Windows Operating System 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. The Security Update Inventory Tool is required for detecting Microsoft Windows and other affected Microsoft products. For more information about the limitations of the Security Update Inventory Tool, see Microsoft Knowledge Base Article 306460

HyperTerminal Vulnerability - CAN-2004-0568:

A remote code execution vulnerability exists in HyperTerminal because of a buffer overrun. An attacker could exploit the vulnerability by constructing a malicious HyperTerminal session file that could potentially allow remote code execution. An attacker could then persuade a user to open this file. This vulnerability could attempt to be exploited through a malicious Telnet URL if HyperTerminal has been set as the default Telnet client. An attacker who successfully exploited this vulnerability could take complete control of an affected system. However, user interaction is required to exploit this vulnerability

Mitigating Factors for HyperTerminal Vulnerability - CAN-2004-0568:

  • By default, Windows Server 2003 does not install HyperTerminal. An administrator must manually install HyperTerminal. If HyperTerminal is installed, it is not set as the preferred Telnet client by default. However, it is still vulnerable to this issue through a specially-crafted HyperTerminal session file.
  • By default, Windows XP, Windows 2000 Server, and Windows NT 4.0 Server do not set HyperTerminal as the preferred Telnet client. However, they are still vulnerable to this issue through a specially-crafted HyperTerminal session file.
  • HyperTerminal, when used on Windows NT 4.0 cannot be set as the default Telnet client. However, Windows NT 4.0 is still vulnerable to this issue through a specially-crafted HyperTerminal session file.
  • Email management best practices that discourage users from opening file attachments with file extensions that are not familiar or that discourage users from opening file attachments from untrusted sources would help to mitigate this vulnerability. The affected file extension (.ht) is not normally used in email and should be treated with caution.
  • 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 Web site. If HyperTerminal has not been set as the default Telnet client, after they click the link, they would be prompted to perform several actions. An attack could only occur after they performed these actions. If HyperTerminal has been set as the default Telnet client, no additional user interaction is required after the user clicks the link that an attacker provides.
  • 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.

Workarounds for HyperTerminal Vulnerability - CAN-2004-0568:

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 or save HyperTerminal Session files (.ht files) that you receive from untrusted sources.
    This vulnerability could be exploited when a user views an .ht file. Do not open files that use this file name extension. Also, these steps do not prevent attacks that occur by using Telnet URLs if HyperTerminal has been set as the default Telnet client.
  • Help prevent e-mail attacks by blocking HyperTerminal session files (.ht files).
    This vulnerability could be exploited when a user views an .ht file. To help block these files by using Outlook and Outlook Express, see Microsoft Knowledge Base Article 837388 and Microsoft Knowledge Base Article 291387. Enterprise customers should consider adding HyperTerminal Session files (.ht files) to the list of unsafe files that are blocked by enterprise gateway e-mail filters.

    Note When you block HyperTerminal session files (.ht files) through e-mail, you are not preventing attacks that use Telnet URLs if HyperTerminal has been set as the default Telnet client.
  • Disable the handler for HyperTerminal session files (.ht files) by removing the following key: HKEY_CLASSES_ROOT\htfile
    If HyperTerminal cannot be removed, delete this key to help reduce attacks. This workaround helps reduce attacks by preventing HyperTerminal from automatically opening HyperTerminal session files (.ht files).

    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 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_CLASSES_ROOT\htfile
    3. Click on htfile, and then press the Delete key on the keyboard.
    4. In the Confirm Key Delete dialog box, click OK. For Windows NT 4.0 Server: In the Warning dialog box, click Yes.

    Impact of Workaround: HyperTerminal session files (.ht files) must be opened manually from within HyperTerminal. Also, these steps do not prevent attacks that occur by using Telnet URLs if HyperTerminal has been set as the default Telnet client.

  • Un-register the HyperTerminal client as the default Telnet client.
    If HyperTerminal cannot be removed, to help prevent attacks that use Telnet URLs, make sure that HyperTerminal has not be set as the default Telnet client. The following steps can help you determine whether HyperTerminal has been set as the default Telnet client. These steps also describe how to un-register HyperTerminal.

    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 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_CLASSES_ROOT\telnet\shell\open\command
    3. If the value C:\Program Files\Windows NT\hypertrm.exe /t %1 exists, change it back to the following default value: rundll32.exe url.dll,TelnetProtocolHandler %l
    4. In Registry Editor, locate the following registry key: HKEY_CURRENT_USER\Software\Netscape\NetscapeNavigator\Viewers\telnet
    5. If the value C:\Program Files\Windows NT\hypertrm.exe /t %1 exists, delete this key. By default, this key does not exist. When you delete this key, you help prevent HyperTerminal from being used by Web browsers other than Internet Explorer as the default Telnet client.

    Impact of Workaround: These changes will help prevent attacks by blocking HyperTerminal from being used to process Telnet URLs. This does not prevent attacks that occur by using HyperTerminal session files (.ht files).

  • Remove HyperTerminal.
    Removing HyperTerminal will help prevent attacks from HyperTerminal session files (.ht files) and from Telnet URLs.

    To remove HyperTerminal, follow these steps:

    • Click Start, click Run, type "%SystemRoot%\System32\rundll32.exe setupapi,InstallHinfSection HypertrmUninstall 132 %SystemRoot%\inf\communic.inf" (without the quotation marks), and then click OK.

      Impact of Workaround: After you remove the HyperTerminal application, any applications that depend on HyperTerminal may fail.

    To reinstall HyperTerminal, follow these steps:  

    • Click Start, click Run, type "%SystemRoot%\System32\rundll32.exe setupapi,InstallHinfSection Hypertrm 132 %SystemRoot%\inf\communic.inf" (without the quotation marks), and then click OK.

      Note To reinstall HyperTerminal after it has been removed, you must have access to your original installation source media.

  • On Windows NT 4.0 Server, on Windows 2000 Server, and on Windows Server 2003, remove HyperTerminal by using the Add/Remove Programs tool in Control Panel.

    To manually remove HyperTerminal from a system, follow these steps. These steps apply only to Windows 2000 Server and Windows Server 2003 and later. For Windows NT 4.0 Server, follow the procedure that is included in the product documentation.

    1. Click Start, point to Settings, and then click Control Panel.
    2. Double-click Add/Remove Programs.
    3. On the left, click Add/Remove Windows Components.
    4. In the Windows Components Wizard, double-click Accessories and Utilities, and then double-click Communications
    5. Make sure that the check box for HyperTerminal is cleared.
    6. Follow the instructions to complete the Windows Components Wizard.

    Impact of Workaround: After you remove the HyperTerminal application, any applications that depend on HyperTerminal may fail.

  • Delete or rename the HyperTerminal program file.

    If HyperTerminal cannot be removed by using the methods that are documented in this section of the security bulletin, you may be able to help prevent attacks by deleting or renaming the physical file.

    Delete or rename the C:\Program Files\Windows NT\hypertrm.exe file.

    Impact of Workaround: After you remove the HyperTerminal application, any applications that depend on HyperTerminal may fail.

FAQ for HyperTerminal Vulnerability - CAN-2004-0568:

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. However, user interaction is required to exploit this vulnerability.

What causes the vulnerability?
An unchecked buffer in the HyperTerminal application.

What is HyperTerminal?
HyperTerminal is an application that you can use to connect to other computers, to Telnet to sites, to bulletin board systems (BBSs), to online services, and to host computers, by using your modem, a null modem cable, or and Ethernet connection. For more information about HyperTerminal, visit this Microsoft Web site.

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?
There are several different ways that an attacker could attempt to exploit this vulnerability. However, user interaction is required to exploit this vulnerability in every case. Here are some examples:

  • An attacker could exploit the vulnerability by constructing a malicious HyperTerminal session file (.ht) and then persuade the user to open the file.
  • If HyperTerminal has been registered as the default Telnet client, an attacker could host a malicious Web site that is designed to exploit this vulnerability through Internet Explorer and then persuade a user to view the Web site.
  • If HyperTerminal has been registered as the default Telnet client, an attacker could also create an e-mail message that has a specially-crafted Telnet URL. An attacker could attempt to exploit this vulnerability by persuading the user to view or to preview an e-mail message than contains a Telnet URL and then persuade the user to then click the Telnet URL.

How do I know if HyperTerminal has been registered as my default Telnet client on Windows 2000 Server?
HyperTerminal will automatically register itself as the default Telnet client the first time that the HyperTerminal application is launched. After HyperTerminal is registered as the default Telnet client, it will automatically start when you click a hyperlink to a Telnet URL in a Web browser or in an e-mail message. If you believe that these steps were performed, you should consider using the workarounds that are required when HyperTerminal has been registered as the default Telnet client that are listed in the Workarounds section of this security bulletin.

How do I know if HyperTerminal has been registered as my default Telnet client on Windows XP?
HyperTerminal will prompt you to register it as the default Telnet client the first time that you start the HyperTerminal application. After HyperTerminal is registered as the default Telnet client, it will automatically start when you click a hyperlink to a Telnet URL in a Web browser or in an e-mail message. If you did not select to register HyperTerminal as the default Telnet client when you are prompted, the system would only be vulnerable if you opened a specially-crafted HyperTerminal session file. If you believe that these steps were performed, you should consider using the workarounds that are required when HyperTerminal has been registered as the default Telnet client that are listed in the Workarounds section of this security bulletin.

How do I know if HyperTerminal has been registered as my default Telnet client on Windows Server 2003?
By default, HyperTerminal is not installed. An administrator would have to manually install HyperTerminal for the system to be vulnerable to this issue. After installation, HyperTerminal will prompt you to register it as the default Telnet client the first time that you start the HyperTerminal application. After HyperTerminal is registered as the default Telnet client, it will automatically start when you click a hyperlink to a Telnet URL in a Web browser or in an e-mail message. If you believe that these steps were performed, you should consider using the workarounds that are required when HyperTerminal has been registered as the default Telnet client that are listed in the Workarounds section of this security bulletin.

HyperTerminal is also included with Windows NT 4.0 Server. Is that version vulnerable to this vulnerability?
Yes. However, the HyperTerminal client that is included with Windows NT 4.0 Server does not include a TCP/IP connection method. Therefore, the Windows NT 4.0 Server HyperTerminal client cannot be registered as the default Telnet client, and would not automatically start in response to a supplied Telnet URL. However, Windows NT 4.0 is still vulnerable to this issue if you open a specially-crafted HyperTerminal session file.

Should I un-register the HyperTerminal client after it has been set as the default Telnet client?
Yes, if you do not use Telnet URLs. If you un-register the HyperTerminal client as the default Telnet client, you help protect systems from malicious Telnet URLs. However, these systems are still vulnerable to this issue if you open a specially-crafted HyperTerminal session file. You can use the workarounds that are listed in the Workarounds section of this security bulletin to help un-register HyperTerminal as the default Telnet client.

Is the built-in Telnet client vulnerable?
No. The default Telnet client is a command-line client (Telnet.exe). The command-line client is not affected by this vulnerability

What is a HyperTerminal session file?
A session file captures all the parameters that are associated with a specific HyperTerminal session. For example, the session file captures the communications parameters and the destination host. When you open a session file, you can automatically set all the HyperTerminal parameters to the parameters that are specified in the file.

What is wrong with the way that HyperTerminal uses session files?
The method that HyperTerminal uses to validate the length of a value that can be saved in a session file.

Could the attacker force the session file to open automatically?
No. Even after an attacker creates the file and delivers it to the user, the attacker still must persuade the user to manually open it. The attacker cannot not force the file to open without the user's interaction.

What systems are primarily at risk from the vulnerability?
All affected operating systems are at risk from this vulnerability. Windows Server 2003 is at a reduced risk because HyperTerminal is not installed by default.

Could the vulnerability be exploited over the Internet?
Yes. An attacker could attempt to exploit this vulnerability over the Internet. Firewall best practices and standard default firewall configurations can help protect against attacks that occur by using Telnet URLs 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 modifying the way that HyperTerminal 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 to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.

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

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-kb873339-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-kb873339-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. To help reduce the chance that a reboot will be required, close all instances of the HyperTerminal application.

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%\$NTUninstallKB873339$\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 NameVersionDateTimeSizeFolder
Hypertrm.dll5.2.3790.23316-Nov-200417:27537,088RTMGDR
Hypertrm.dll5.2.3790.23316-Nov-200417:21537,088RTMQFE

Windows Server 2003 64-Bit Enterprise Edition and Windows Server 2003 64-Bit Datacenter Edition:

File NameVersionDateTimeSizeCPUFolder
Hypertrm.dll5.2.3790.23316-Nov-200417:311,879,040IA-64RTMGDR
Hypertrm.dll5.2.3790.23316-Nov-200417:301,879,040IA-64RTMQFE

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\KB873339\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 873339 security update into the Windows installation source files.

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-kb873339-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-kb873339-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. To help reduce the chance that a reboot will be required, close all instances of the HyperTerminal application.

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%\$NTUninstallKB873339$\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 NameVersionDateTimeSizeFolder
Hypertrm.dll5.1.2600.160917-Nov-200417:57493,056SP1QFE
Hypertrm.dll5.1.2600.256317-Nov-200417:41347,136SP2GDR
Hypertrm.dll5.1.2600.256317-Nov-200417:31347,136SP2QFE

Windows XP 64-Bit Edition Service Pack 1:

File NameVersionDateTimeSizeCPUFolder
Hypertrm.dll5.1.2600.160917-Nov-200417:551,849,344IA-64SP1QFE
Whypertrm.dll5.1.2600.160917-Nov-200417:57493,056x86WOW

Windows XP 64-Bit Edition Version 2003:

File NameVersionDateTimeSizeCPUFolder
Hypertrm.dll5.2.3790.23316-Nov-200417:311,879,040IA-64RTMGDR
Hypertrm.dll5.2.3790.23316-Nov-200417:301,879,040IA-64RTMQFE

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\KB873339\Filelist

    For Windows XP 64-Bit Edition Version 2003:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP1\KB873339\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 873339 security update into the Windows installation source files.

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-kb873339-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-kb873339-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. To help reduce the chance that a reboot will be required, close all instances of the HyperTerminal application.

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%\$NTUninstallKB873339$\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 NameVersionDateTimeSize
Hypertrm.dll5.0.2195.700016-Nov-200410:47576,784

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\KB873339\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 873339 security update into the Windows installation source files.

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-kb873339-x86-enu /q

For Windows NT Server 4.0 Terminal Server Edition:

Windowsnt4terminalserver-kb873339-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-kb873339-x86-enu /z

For Windows NT Server 4.0 Terminal Server Edition:

Windowsnt4terminalserver-kb873339-x86-enu /z

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. To help reduce the chance that a reboot will be required, close all instances of the HyperTerminal application.

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%\$NTUninstallKB873339$ 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 NameVersionDateTimeSize
Hypertrm.dll4.0.1381.732314-Nov-200417:22404,752

Windows NT Server 4.0 Terminal Server Edition:

File NameVersionDateTimeSize
Hypertrm.dll4.0.1381.84214-Nov-200417:31404,240

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\KB873339\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 873339 security update into the Windows installation source files.

Other Information

Acknowledgments

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

Obtaining Other Security Updates:

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

Support:

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

Security Resources:

Software Update Services:

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

For more information about how to deploy 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

Built at 2014-04-18T13:49:36Z-07:00

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2015 Microsoft