Computer Security
[EN] securityvulns.ru no-pyccku


Related information

  Multiple system telnet client information leak

  iDEFENSE Security Advisory 06.14.05: Multiple Vendor Telnet Client Information Disclosure Vulnerability

From:MICROSOFT <secure_(at)_microsoft.com>
Date:15.06.2005
Subject:Microsoft Security Bulletin MS05-033 Vulnerability in Telnet Client Could Allow Information Disclosure (896428)

 Microsoft Security Bulletin MS05-033
 Vulnerability in Telnet Client Could Allow Information Disclosure (896428)
 
 Issued: June 14, 2005
 Version: 1.0
 Summary
 
 Who should read this document: Customers who use a Microsoft Telnet client
 
 Impact of Vulnerability: Information Disclosure
 
 Maximum Severity Rating: Moderate
 
 Recommendation: Customers should consider applying the security update.
 
 Security Update Replacement: None
 
 Caveats: None
 
 Tested Software and Security Update Download Locations:
 
 Affected Software:
 •
 
 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 (Itanium) – Download the update
 •
 
 Microsoft Windows XP 64-Bit Edition Version 2003 (Itanium) – Download the update
 •
 
 Microsoft Windows XP Professional x64 Edition – Download the update
 •
 
 Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 – Download the update
 •
 
 Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems – Download the update
 •
 
 Microsoft Windows Server 2003 x64 Edition – Download the update
 •
 
 Microsoft Windows Services for UNIX 3.5 when running on Windows 2000 – Download the update
 •
 
 Microsoft Windows Services for UNIX 3.0 when running on Windows 2000 – Download the update
 •
 
 Microsoft Windows Services for UNIX 2.2 when running on Windows 2000 – Download the update
 
 Non-Affected Software:
 •
 
 Microsoft Windows 2000 Service Pack 3 and Microsoft Windows 2000 Service Pack 4
 •
 
 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 whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.
 Top of sectionTop of section
 General Information
 
 Executive Summary
 
 Executive Summary:
 
 This update resolves a newly-discovered, privately-reported vulnerability. An attacker who successfully exploited this information disclosure vulnerability could remotely read the session variables for users who have open connections to a malicious telnet server. The vulnerability is documented in the “Vulnerability Details” section of this bulletin.
 
 We recommend that customers consider applying the security update.
 
 Severity Ratings and Vulnerability Identifiers:
 Vulnerability Identifiers Impact of Vulnerability Windows XP Service Pack 1 Windows XP Service Pack 2 Windows Server 2003 Windows Server 2003 Service Pack 1 Windows Services for UNIX (All versions)
 
 Telnet Vulnerability - CAN-2005-1205
 
 
 Information Disclosure
 
 
 Moderate
 
 
 Moderate
 
 
 Moderate
 
 
 Moderate
 
 
 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.
 
 Note The severity ratings for non-x86 operating system versions map to the x86 operating systems versions as follows:
 •
 
 The Microsoft Windows XP 64-Bit Edition Service Pack 1 (Itanium) severity rating is the same as the Windows XP Service Pack 1 severity rating.
 •
 
 The Microsoft Windows XP 64-Bit Edition Version 2003 (Itanium) severity rating is the same as the Windows XP Service Pack 1 severity rating.
 •
 
 The Microsoft Windows XP Professional x64 Edition severity rating is the same as the Windows XP Service Pack 2 severity rating.
 •
 
 The Microsoft Windows Server 2003 for Itanium-based Systems severity rating is the same as the Windows Server 2003 severity rating.
 •
 
 The Microsoft Windows Server 2003 with SP1 for Itanium-based Systems severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating.
 •
 
 The Microsoft Windows Server 2003 x64 Edition severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating.
 Top of sectionTop of section
 
 Frequently asked questions (FAQ) related to this security update
 
 Does this update contain any other changes to functionality?
 Yes. In addition to the changes that are listed in each “Vulnerability Details” sections of this bulletin, this update includes the following change in functionality: A new registry key was added to allow customers to specify additional environment variables that the telnet client can disclose. For more information, see Microsoft Knowledge Base Article 900934
 
 Extended security update support for Microsoft Windows NT Workstation 4.0 Service Pack 6a and Windows 2000 Service Pack 2 ended on June 30, 2004. Extended security update support for Microsoft Windows NT Server 4.0 Service Pack 6a ended on December 31, 2004. I’m still using one of these operating systems, what should I do?
 
 Windows NT Workstation 4.0 Service Pack 6a, Windows NT Server 4.0 Service Pack 6a, and Windows 2000 Service Pack 2 have reached the end of their life cycles. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.
 
 Customers who require additional support for Windows NT 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 without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager.
 
 For more information, see the Windows Operating System Product Support Lifecycle FAQ.
 
 Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine whether this update is required?
 Yes. MBSA will determine whether this update is required, but only for programs that MBSA supports. For example, MBSA does not support Windows Services for UNIX and will not detect whether the update is required for that program. However, Microsoft has developed a version of the Enterprise Update Scanning Tool (EST) that will help customers determine if the Windows Services for UNIX security update is required. For detailed information about the programs that MBSA currently does not detect, see Microsoft Knowledge Base Article 306460. For more information about MBSA, visit the MBSA Web site.
 
 What is the Enterprise Update Scanning Tool (EST)?
 As part of an ongoing commitment to provide detection tools for bulletin-class security updates, Microsoft delivers a stand-alone detection tool whenever the Microsoft Baseline Security Analyzer (MBSA) and the Office Detection Tool (ODT) cannot detect whether the update is required for an MSRC release cycle. This stand-alone tool is called the Enterprise Update Scanning Tool (EST) and is designed for enterprise administrators. When a version of the Enterprise Update Scanning Tool is created for a specific bulletin, customers can run the tool from a command line interface (CLI) and view the results of the XML output file. To help customers better utilize the tool, detailed documentation will be provided with the tool. There is also a version of the tool that offers an integrated experience for SMS administrators.
 
 Can I use a version of the Enterprise Update Scanning Tool (EST) to determine whether this update is required?
 Yes. Microsoft has created a version of the EST that will determine if you have to apply the Windows Services for UNIX updates. For more information about the version of the EST that is being released this month, see the following Microsoft Web site. For more detailed deployment information about the version of the EST that is being released this month, see the following Microsoft Web site. There is also a version of this tool that SMS customers can obtain by visiting the following Microsoft Web site. This tool may also be available for SMS customers from the SMS Web site.
 
 Can I use Systems Management Server (SMS) to determine whether this update is required?
 Yes. SMS can help detect and deploy this security update. SMS uses MBSA for detection; therefore, SMS has the same limitation listed earlier in this bulletin related to programs that MBSA does not detect. However, there is a version of the EST that SMS customers can obtain that offers an integrated experience for SMS administrators. To download this version of the EST, visit the following Microsoft 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
 Top of sectionTop of section
 
 Vulnerability Details
 
 Telnet Vulnerability - CAN-2005-1205:
 
 An attacker who successfully exploited this information disclosure vulnerability could remotely read the session variables for users who have open connections to a malicious telnet server.
 
 Mitigating Factors for Telnet Vulnerability - CAN-2005-1205:
 •
 
 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.
 •
 
 An attacker who successfully exploited this vulnerability could only read the session variables for the affected user. This does not include critical data such as password hashes.
 •
 
 All versions of Windows Services for UNIX are vulnerable to this issue only when they are running on Windows 2000. When Windows Services for UNIX is running on other operating systems, it is not vulnerable to this issue.
 Top of sectionTop of section
 
 Workarounds for Telnet Vulnerability - CAN-2005-1205:
 
 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 in the following section.
 •
 
 Un-register the default Telnet client:
 To help prevent attacks that use Telnet URLs, you can remove the Telnet, Tn3270, and Rlogin handlers. This will prevent Internet Explorer and other applications from automatically launching Telnet sessions.
 
 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 that you back 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, delete the following registry keys:
 
 HKEY_CLASSES_ROOT\telnet\shell\open\command
 HKEY_CLASSES_ROOT\tn3270\shell\open\command
 HKEY_CLASSES_ROOT\rlogin\shell\open\command
 
 Impact of Workaround: These changes will help prevent attacks by blocking Telnet from being used to process Telnet, Tn3270, or Rlogin URLs.
 Top of sectionTop of section
 
 FAQ for Telnet Vulnerability - CAN-2005-1205:
 
 What is the scope of the vulnerability
 This is an information disclosure vulnerability. An attacker who successfully exploited this vulnerability could remotely read the session variables of users who have open connections to a malicious telnet server. Note that this vulnerability would not allow an attacker to execute code or to elevate their user rights directly. It could be used to produce useful information to try to further compromise the affected system.
 
 What causes the vulnerability?
 The Telnet client was designed to provide this kind of information.
 
 What is Telnet?
 Telnet is an industry standard protocol that allows a user to establish a remote terminal session on a telnet server. Because this is a terminal session, there is only a command-line interface. Telnet is mainly used for simple remote administration at a command prompt. This is a separate application than Microsoft HyperTerminal. Microsoft HyperTerminal is not affected by this issue.
 
 What is Microsoft Windows Services for UNIX?
 Microsoft Windows Services for UNIX is a product that allows customers to run UNIX application on a Windows system. Providing this capability expands support for UNIX applications, daemons, and scripts by providing an enhanced UNIX environmental subsystem beyond the standard POSIX subsystem. Windows Service for UNIX allows customers to run UNIX applications, daemons, and scripts.
 
 What might an attacker use the vulnerability to do?
 An attacker who successfully exploited this vulnerability could remotely read the session variables for users who have open connections to a malicious telnet server.
 
 Who could exploit the vulnerability?
 Any anonymous user who could deliver a specially crafted message to the affected system could try to exploit this vulnerability.
 
 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 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.
 •
 
 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.
 
 What systems are primarily at risk from the vulnerability?
 All affected operating systems are at risk from this vulnerability. However, an attacker would have to combine this issue with another vulnerability for a system to be at risk.
 
 What does the update do?
 The update removes the vulnerability by restricting the session variables that Telnet sends to a Telnet server. Internet RFC 1572 defines a set of “well known” variables that the updated Telnet client allows to be requested. This updated Telnet client also continues to allow the use of the SFUTLNTVER and SFUTLNTMODE variables because they are used by Windows Services for UNIX Telnet servers. All other session variables are restricted.
 
 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.
 Top of sectionTop of section
 Top of sectionTop of section
 Top of sectionTop of section
 
 Security Update Information
 
 Affected Software:
 
 For information about the specific security update for your affected software, click the appropriate link:
 
 Windows Server 2003 (all versions)
 
 Prerequisites
 This security update requires Windows Server 2003 or Windows Server 2003 Service Pack 1.
 
 Inclusion in Future Service Packs:
 The update for this issue will be included in future Service Pack or Update Rollup.
 
 Installation Information
 
 This security update supports the following setup switches.
 Supported Security Update Installation Switches
 Switch Description
 
 /help
 
 
 Displays the command-line options
 Setup Modes
 
 /passive
 
 
 Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
 
 /quiet
 
 
 Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
 Restart Options
 
 /norestart
 
 
 Does not restart when installation has completed
 
 /forcerestart
 
 
 Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
 
 /warnrestart[:x]
 
 
 Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switches.
 
 /promptrestart
 
 
 Display a dialog box prompting the local user to allow a restart
 Special Options
 
 /overwriteoem
 
 
 Overwrites OEM files without prompting
 
 /nobackup
 
 
 Does not backup files needed for uninstall
 
 /forceappsclose
 
 
 Forces other programs to close when the computer shuts down
 
 /log:path
 
 
 Allows the redirection of installation log files
 
 /integrate:path
 
 
 Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
 
 /extract[:path]
 
 
 Extracts files without starting the Setup program
 
 /ER
 
 
 Enables extended error reporting
 
 /verbose
 
 
 Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.
 
 Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. 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-kb896428-x86-enu /quiet
 
 Note Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB896428.log file for any failure messages when they use this switch.
 
 To install the security update without forcing the system to restart, use the following command at a command prompt for Windows Server 2003:
 
 Windowsserver2003-kb896428-x86-enu /norestart
 
 For information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site.
 
 Restart Requirement
 
 This update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a reboot will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.
 
 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%\$NTUninstallKB896428$\Spuninst folder.
 Supported Spuninst.exe Switches
 Switch Description
 
 /help
 
 
 Displays the command-line options
 Setup Modes
 
 /passive
 
 
 Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
 
 /quiet
 
 
 Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
 Restart Options
 
 /norestart
 
 
 Does not restart when installation has completed
 
 /forcerestart
 
 
 Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
 
 /warnrestart[:x]
 
 
 Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switches.
 
 /promptrestart
 
 
 Display a dialog box prompting the local user to allow a restart
 Special Options
 
 /forceappsclose
 
 
 Forces other programs to close when the computer shuts down
 
 /log:path
 
 
 Allows the redirection of installation log files
 
 File Information
 
 The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
 
 Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Datacenter Edition; Windows Server 2003, Enterprise Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; and Windows Server 2003, Datacenter Edition with SP1:
 File Name Version Date Time Size Folder
 
 Telnet.exe
 
 
 5.2.3790.329
 
 
 10-May-2005
 
 
 23:59
 
 
 73,728
 
 
 RTMGDR
 
 Telnet.exe
 
 
 5.2.3790.329
 
 
 10-May-2005
 
 
 23:58
 
 
 73,728
 
 
 RTMQFE
 
 Telnet.exe
 
 
 5.2.3790.2442
 
 
 11-May-2005
 
 
 00:44
 
 
 75,776
 
 
 SP1GDR
 
 Telnet.exe
 
 
 5.2.3790.2442
 
 
 11-May-2005
 
 
 00:44
 
 
 75,776
 
 
 SP1QFE
 
 Windows Server, 2003 Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; and Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems:
 File Name Version Date Time Size CPU Folder
 
 Telnet.exe
 
 
 5.2.3790.329
 
 
 11-May-2005
 
 
 14:02
 
 
 182,784
 
 
 IA-64
 
 
 RTMGDR
 
 Telnet.exe
 
 
 5.2.3790.329
 
 
 11-May-2005
 
 
 14:02
 
 
 182,784
 
 
 IA-64
 
 
 RTMQFE
 
 Telnet.exe
 
 
 5.2.3790.2442
 
 
 11-May-2005
 
 
 14:02
 
 
 194,560
 
 
 IA-64
 
 
 SP1GDR
 
 Telnet.exe
 
 
 5.2.3790.2442
 
 
 11-May-2005
 
 
 14:02
 
 
 194,560
 
 
 IA-64
 
 
 SP1QFE
 
 Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition:
 File Name Version Date Time Size CPU Folder
 
 Telnet.exe
 
 
 5.2.3790.2442
 
 
 11-May-2005
 
 
 14:01
 
 
 103,936
 
 
 x64
 
 
 SP1GDR
 
 Telnet.exe
 
 
 5.2.3790.2442
 
 
 11-May-2005
 
 
 14:01
 
 
 103,936
 
 
 x64
 
 
 SP1QFE
 
 Note When you install this security update on Windows Server 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, 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 that the Update Has Been Applied
 •
 
 Microsoft Baseline Security Analyzer
 
 To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.
 •
 
 File Version Verification
 
 Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
 
 1.
 
 
 Click Start, and then click Search.
 
 2.
 
 
 In the Search Results pane, click All files and folders under Search Companion.
 
 3.
 
 
 In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
 
 4.
 
 
 In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
 
 Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
 
 5.
 
 
 On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.
 
 Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
 •
 
 Registry Key Verification
 
 You may also be able to verify the files that this security update has installed by reviewing the following registry keys.
 
 Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; Windows Server 2003, Datacenter Edition with SP1; Windows Server 2003, Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems; Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition:
 
 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP2\KB896428\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 896428 security update into the Windows installation source files.
 Top of sectionTop of section
 
 
 Windows XP (all versions)
 
 Prerequisites
 This security update requires Microsoft Windows XP Service Pack 1 or a later version. For more information, see Microsoft Knowledge Base Article 322389.
 
 Inclusion in Future Service Packs:
 The update for this issue will be included in a future Service Pack or Update Rollup.
 
 Installation Information
 
 This security update supports the following setup switches.
 Supported Security Update Installation Switches
 Switch Description
 
 /help
 
 
 Displays the command-line options
 Setup Modes
 
 /passive
 
 
 Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
 
 /quiet
 
 
 Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
 Restart Options
 
 /norestart
 
 
 Does not restart when installation has completed
 
 /forcerestart
 
 
 Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
 
 /warnrestart[:x]
 
 
 Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switches.
 
 /promptrestart
 
 
 Display a dialog box prompting the local user to allow a restart
 Special Options
 
 /overwriteoem
 
 
 Overwrites OEM files without prompting
 
 /nobackup
 
 
 Does not backup files needed for uninstall
 
 /forceappsclose
 
 
 Forces other programs to close when the computer shuts down
 
 /log:path
 
 
 Allows the redirection of installation log files
 
 /integrate:path
 
 
 Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
 
 /extract[:path]
 
 
 Extracts files without starting the Setup program
 
 /ER
 
 
 Enables extended error reporting
 
 /verbose
 
 
 Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.
 
 Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. 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 Microsoft Windows XP:
 
 Windowsxp-kb896428-x86-enu /quiet
 
 Note Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB896428.log file for any failure messages when they use this switch.
 
 To install the security update without forcing the system to restart, use the following command at a command prompt for Windows XP:
 
 Windowsxp-kb896428-x86-enu /norestart
 
 For information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site.
 
 Restart Requirement
 
 This update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a reboot will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.
 
 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%\$NTUninstallKB896428$\Spuninst folder.
 Supported Spuninst.exe Switches
 Switch Description
 
 /help
 
 
 Displays the command-line options
 Setup Modes
 
 /passive
 
 
 Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
 
 /quiet
 
 
 Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
 Restart Options
 
 /norestart
 
 
 Does not restart when installation has completed
 
 /forcerestart
 
 
 Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
 
 /warnrestart[:x]
 
 
 Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switches.
 
 /promptrestart
 
 
 Display a dialog box prompting the local user to allow a restart
 Special Options
 
 /forceappsclose
 
 
 Forces other programs to close when the computer shuts down
 
 /log:path
 
 
 Allows the redirection of installation log files
 
 File Information
 
 The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
 
 Windows 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
 
 Telnet.exe
 
 
 5.1.2600.1684
 
 
 11-May-2005
 
 
 00:09
 
 
 72,192
 
 
 SP1QFE
 
 Telnet.exe
 
 
 5.1.2600.2674
 
 
 10-May-2005
 
 
 23:45
 
 
 75,776
 
 
 SP2GDR
 
 Telnet.exe
 
 
 5.1.2600.2674
 
 
 10-May-2005
 
 
 23:51
 
 
 75,776
 
 
 SP2QFE
 
 Windows XP 64-Bit Edition Service Pack 1 (Itanium):
 File Name Version Date Time Size CPU Folder
 
 Telnet.exe
 
 
 5.1.2600.1684
 
 
 11-May-2005
 
 
 00:19
 
 
 197,632
 
 
 IA-64
 
 
 SP1QFE
 
 Wtelnet.exe
 
 
 5.1.2600.1684
 
 
 11-May-2005
 
 
 00:09
 
 
 72,192
 
 
 x86
 
 
 SP1QFE\WOW
 
 Windows XP 64-Bit Edition Version 2003 (Itanium):
 File Name Version Date Time Size CPU Folder
 
 Telnet.exe
 
 
 5.2.3790.329
 
 
 11-May-2005
 
 
 14:02
 
 
 182,784
 
 
 IA-64
 
 
 RTMGDR
 
 Telnet.exe
 
 
 5.2.3790.329
 
 
 11-May-2005
 
 
 14:02
 
 
 182,784
 
 
 IA-64
 
 
 RTMQFE
 
 Telnet.exe
 
 
 5.2.3790.2442
 
 
 11-May-2005
 
 
 14:02
 
 
 194,560
 
 
 IA-64
 
 
 SP1GDR
 
 Telnet.exe
 
 
 5.2.3790.2442
 
 
 11-May-2005
 
 
 14:02
 
 
 194,560
 
 
 IA-64
 
 
 SP1QFE
 
 Windows XP Professional x64:
 File Name Version Date Time Size CPU Folder
 
 Telnet.exe
 
 
 5.2.3790.2442
 
 
 11-May-2005
 
 
 14:01
 
 
 103,936
 
 
 x64
 
 
 SP1GDR
 
 Telnet.exe
 
 
 5.2.3790.2442
 
 
 11-May-2005
 
 
 14:01
 
 
 103,936
 
 
 x64
 
 
 SP1QFE
 
 Notes The Windows XP security update is packaged as a dual-mode package. 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 these security updates, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.If you have previously installed a hotfix to update 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 (Itanium)
 
 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 (Itanium)
 
 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.
 
 Note For Windows XP 64-Bit Edition Version 2003 (Itanium), this security update is the same as the Windows Server 2003 for Itanium-based Systems security update.
 
 Verifying that the Update Has Been Applied
 •
 
 Microsoft Baseline Security Analyzer
 
 To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.
 •
 
 File Version Verification
 
 Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
 
 1.
 
 
 Click Start, and then click Search.
 
 2.
 
 
 In the Search Results pane, click All files and folders under Search Companion.
 
 3.
 
 
 In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
 
 4.
 
 
 In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
 
 Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
 
 5.
 
 
 On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.
 
 Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
 •
 
 Registry Key Verification
 
 You may also be able to verify the files that this security update has installed by reviewing the following registry keys.
 
 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\KB896428\Filelist
 
 For Windows XP 64-Bit Edition Version 2003 (Itanium):
 
 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP1\KB896428\Filelist
 
 For Windows XP Professional x64
 
 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP2\KB896428\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 896428 security update into the Windows installation source files.
 Top of sectionTop of section
 
 
 Windows Services for UNIX (all versions)
 
 Prerequisites
 This security update requires Windows Services for UNIX versions 2.2, 3.0, or 3.5 running on Windows 2000.
 
 The software that is listed has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.
 
 Installation Information
 
 This security update supports the following setup switches.
 Supported Hotfix.exe Installation Switches
 Switch Description
 
 /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 finishes
 
 /q
 
 
 Use Quiet or Unattended mode without a 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 Services for UNIX 2.2:
 
 SFU22-KB896428-W2K-X86-ENU.exe /q
 
 For Windows Services for UNIX 3.0:
 
 SFU3-KB896428-W2K-X86-ENU.exe /q
 
 For Windows Services for UNIX 3.5:
 
 SFU35-KB896428-W2K-X86-ENU.exe /q
 
 Restart Requirement
 
 This update does not require a restart. For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.
 
 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%\$NTUninstallKB896428$ folder.
 Supported Hotfix.exe Installation Switches
 Switch Description
 
 /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 finishes
 
 /q
 
 
 Use Quiet or Unattended mode without a user interface (this switch is a superset of /m)
 
 /m
 
 
 Use Unattended mode with a user interface
 
 /l
 
 
 List the installed hotfixes
 
 File Information
 
 The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
 
 Windows Services for UNIX 2.2:
 File Name Version Date Time Size
 
 Telnetc.exe
 
 
 5.3000.2073.13
 
 
 25-May-2005
 
 
 19:19
 
 
 120,832
 
 Windows Services for UNIX 3.0:
 File Name Version Date Time Size
 
 Telnetc.exe
 
 
 7.0.1701.44
 
 
 25-May-2005
 
 
 18:50
 
 
 122,368
 
 Windows Services for UNIX 3.5:
 File Name Version Date Time Size
 
 Telnetc.exe
 
 
 8.0.1969.33
 
 
 25-May-2005
 
 
 18:59
 
 
 123,392
 
 Verifying that the Update Has Been Applied
 •
 
 File Version Verification
 
 Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
 
 1.
 
 
 Click Start, and then click Search.
 
 2.
 
 
 In the Search Results pane, click All files and folders under Search Companion.
 
 3.
 
 
 In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
 
 4.
 
 
 In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
 
 Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
 
 5.
 
 
 On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.
 
 Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
 •
 
 Registry Key Verification
 
 You may also be able to verify the files that this security update has installed by reviewing the following registry key:
 
 HKLM\SOFTWARE\Microsoft\Updates\Microsoft Services for UNIX\KB896428\PackageName
 Top of sectionTop of section
 Top of sectionTop of section
 
 Acknowledgments
 
 Microsoft thanks the following for working with us to help protect customers:
 •
 
 iDEFENSE for reporting the Telnet Vulnerability (CAN-2005-1205).
 
 Obtaining Other Security Updates:
 
 Updates for other security issues are available at the following locations:
 •
 
 Security updates are available in the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch."
 •
 
 Updates for consumer platforms are available at 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 by using 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 can 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 Analyze, Microsoft Office Detection Tool, and the Enterprise Update Scanning 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, visit 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 (June 14, 2005): Bulletin published

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