Export (0) Print
Expand All

Microsoft Security Bulletin MS04-036 - Critical

Vulnerability in NNTP Could Allow Remote Code Execution (883935)

Published: October 12, 2004

Version: 1.0

Issued: October 12, 2004
Version: 1.0

Summary

Who should read this document: Customers who use Microsoft Windows or Microsoft Exchange Server

Impact of Vulnerability: Remote Code Execution

Maximum Severity Rating: Critical

Recommendation: Customers should apply the update immediately.

Security Update Replacement: None

Caveats: None

Tested Software and Security Update Download Locations:

Affected Software:

  • Microsoft Windows NT Server 4.0 Service Pack 6a – Download the update
  • Microsoft Windows 2000 Server Service Pack 3 and Microsoft Windows 2000 Server Service Pack 4 – Download the update
  • Microsoft Windows Server™ 2003 – Download the update
  • Microsoft Windows Server 2003 64-Bit Edition – Download the update
  • Microsoft Exchange 2000 Server Service Pack 3 (Uses the Windows 2000 NNTP component)
  • Microsoft Exchange Server 2003 and Microsoft Exchange Server 2003 Service Pack 1 (Uses the Windows 2000 or Windows Server 2003 NNTP component)

Non-Affected Software:

  • Microsoft Windows NT Server 4.0 Terminal Server Edition Service Pack 6
  • Microsoft Windows 2000 Professional Service Pack 3 and Microsoft Windows 2000 Professional Service Pack 4
  • Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2
  • Microsoft Windows XP 64-Bit Edition Service Pack 1
  • Microsoft Windows XP 64-Bit Edition Version 2003
  • Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE), and Microsoft Windows Millennium Edition (ME)
  • Microsoft Exchange Server 5.0 Service Pack 2
  • Microsoft Exchange Server 5.5 Service Pack 4

Tested Microsoft Windows Components:

Affected Components:

  • Microsoft Windows NT Server 4.0 Service Pack 6a NNTP component
  • Microsoft Windows 2000 Server Service Pack 3 NNTP component and Microsoft Windows 2000 Server Service Pack 4 NNTP component
  • Microsoft Windows Server 2003 NNTP Component
  • Microsoft Windows Server 2003 64-Bit Edition NNTP Component

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. A remote code execution vulnerability exists within the Network News Transfer Protocol (NNTP) component of the affected operating systems. This vulnerability could potentially affect systems that do not use NNTP. This is because some programs that are listed in the affected software section require that the NNTP component be enabled before you can install them. The vulnerability is documented in the Vulnerability Details section of this bulletin.

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 that have full privileges.

We recommend that customers apply the update immediately.

Severity Ratings and Vulnerability Identifiers:

Vulnerability IdentifiersImpact of VulnerabilityExchange 2000 ServerExchange Server 2003Windows NT Server 4.0Windows 2000 ServerWindows Server 2003
NNTP Vulnerability - CAN-2004-0574Remote Code ExecutionCriticalImportantImportantImportantImportant

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.

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 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. SMS can search for the existence of the affected files documented in the Security Update Information section of this bulletin. Update all versions of affected files that are earlier than versions documented in this security bulletin. For information about SMS, visit the SMS Web site.

NNTP Vulnerability - CAN-2004-0574:

A remote code execution vulnerability exists within the Network News Transfer Protocol (NNTP) component of the affected operating systems. This vulnerability could potentially affect systems that do not use NNTP. This is because some programs that are listed in the affected software section require that the NNTP component be enabled before you can install them. An attacker could exploit the vulnerability by constructing a malicious request that could potentially allow remote code execution. An attacker who successfully exploited this vulnerability could take complete control of an affected system.

Mitigating Factors for NNTP Vulnerability - CAN-2004-0574:

  • Firewall best practices and standard default firewall configurations can help protect networks from attacks that originate outside the enterprise perimeter. Best practices recommend that systems that are connected to the Internet have a minimal number of ports exposed. If the affected NNTP Ports (119 and 563) are blocked at the firewall, external attacks attempting to exploit this vulnerability could be blocked.
  • Windows NT Server 4.0, Windows 2000 Server, and Windows Server 2003 are at a reduced risk from this vulnerability because the affected component is not installed by default. Even if Internet Information Services is installed, the affected component is not installed by default. An administrator must manually install the affected component for a system to become vulnerable to this issue.
  • Exchange 2000 Server and Exchange Server 2003 require the installation of the affected operating system component. However upon installation, Exchange Server 2003 disables the affected operating system component. Exchange Server 2003 requires an administrator to manually re-enable this component to become vulnerable to this issue. Exchange 2000 Server does not disable this component by default when it is installed. However, if an administrator manually disables this component after installing Exchange Server 2000, the system is not vulnerable to this issue. Best practice recommendations for helping to secure Exchange 2000 Server include disabling the affected operating system component. For more information about how to help secure Exchange 2000 Server, visit the following Web site.

Workarounds for NNTP Vulnerability - CAN-2004-0574:

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.

  • Block the following at the firewall:
    • UDP ports 119 and 563
    • TCP ports 119 and 563

    These ports are used to initiate a connection with a NNTP server. Blocking them at the firewall will help prevent systems that are behind that firewall from attempts to exploit this vulnerability. Also, make sure that you block any other specifically configured NNTP ports on the system. We recommend that you block all unsolicited inbound communication from the Internet to help prevent attacks that may use other ports. For more information about the ports that NNTP uses, visit the following Web site. Port 563 is the default port that NNTP uses to perform Secure Sockets Layer (SSL) connections.

  • Enable advanced TCP/IP filtering on systems that support this feature.

    You can enable advanced TCP/IP filtering to block the affected ports and to block all unsolicited inbound traffic. For more information about how to configure TCP/IP filtering, see Microsoft Knowledge Base Article 309798.

  • Block the affected ports by using IPSec on the affected systems.

    Use Internet Protocol security (IPSec) to help protect network communications. Detailed information about IPSec and how to apply filters is available in Microsoft Knowledge Base Articles 313190 and 813878.

  • Remove or disable NNTP if you do not need it:

    In many organizations, NNTP only provides services for legacy systems. If you no longer need NNTP, you could remove it by following these steps. These steps apply only to Windows 2000 and later versions. For Windows NT 4.0, follow the procedure that is included in the product documentation. NNTP is a required component for Exchange 2000 Server and Exchange Server 2003. However, while NNTP may not be removed on Exchange servers, it can be disabled. NNTP is disabled by default on Exchange 2003. To help secure Exchange 2000 systems, follow the Securing Exchange 2000 Server best practice recommendations instead of these instructions.

    To remove NNTP components and services:

    1. In Control Panel, click Add or Remove Programs.
    2. Click Add/Remove Windows Components.
    3. On the Windows Components Wizard page, under Components, click Internet Information Services (IIS), and then click Details.
    4. Click to clear the Network News Transfer Protocol Service (NNTP) check box to remove NNTP.
    5. Complete the Windows Components Wizard by following the instructions on the screen.

    Impact of Workaround: NNTP services will no longer function. Any applications or services that require NNTP may fail. Administrators should not remove NNTP unless they fully understand the affect that doing so will have on their network. For more information about NNTP, see the NNTP product documentation.

FAQ for NNTP Vulnerability - CAN-2004-0574:

What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could remotely take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts that have full privileges. This vulnerability could potentially affect systems that do not use NNTP. This is because some programs that are listed in the affected software section require that the NNTP component be enabled before you can install them.

What causes the vulnerability?
An unchecked buffer in the Network News Transfer Protocol (NNTP) component.

What is the Network News Transfer Protocol (NNTP) component?
The NNTP component provides a service that enables the distribution, retrieval, and posting of news articles among the Internet community. NNTP is designed so that news articles are stored in a central database allowing a subscriber to select only those items that they want to read. For more information about NNTP, see the NNTP product documentation. NNTP is defined in Request for Comment (RFC) documents 977 and 2980.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system.

Who could exploit the vulnerability?
Any anonymous user who could deliver a specially crafted message to the affected system could attempt to exploit this vulnerability.

How could an attacker exploit the vulnerability?
An attacker could exploit the vulnerability by creating a specially crafted message and sending the message to an affected system, which could then cause the affected system to execute code.

An attacker could also access the affected component through another vector. For example, an attacker could log on to the system interactively or by using another program that passes parameters to the vulnerable component (locally or remotely).

What systems are primarily at risk from the vulnerability?
Windows 2000 Professional (all versions), and Windows XP (all versions) are not affected by this vulnerability. The affected component is not supported on these operating system versions.

Windows NT Server 4.0, Windows 2000 Server, and Windows Server 2003 are at a reduced risk from this vulnerability because the affected component is not installed by default. Even if Internet Information Services (IIS) is installed, the affected component is not installed by default.

Exchange 2000 servers and systems that have manually enabled NNTP are primarily at risk from this vulnerability. Exchange 2000 Server and Exchange Server 2003 require the installation of the affected operating system component. However upon installation, Exchange Server 2003 disables the affected operating system component. Exchange Server 2003 requires an administrator to manually re-enable this component to become vulnerable to this issue. Exchange 2000 Server does not disable this component by default when it is installed. However, if an administrator manually disables this component after installing Exchange Server 2000, the system is not vulnerable to this issue. Best practice recommendations for helping to secure Exchange 2000 Server include disabling the affected operating system component. For more information about how to help secure Exchange 2000 Server, visit the following Web site.

I use Windows NT Server 4.0 Terminal Server Edition Service Pack 6. Could I be affected by this vulnerability?
No. The NNTP component ships as part of the Windows NT 4.0 Option Pack. The Windows NT 4.0 Option Pack is not supported on this operating system version. For more information, see Microsoft Knowledge Base Article 190157.

If NNTP is installed and running, is it vulnerable?
Yes, except for the Exchange 5.5 Server version of the NNTP Component.

Is Exchange 5.5 Server affected by this vulnerability? 
Exchange 5.5 Server and Exchange 5.0 Server are not affected by this vulnerability. Their implementation of NNTP is independent of the implementation in other affected software versions.

Could the vulnerability be exploited over the Internet?
Yes. An attacker may be able to exploit this vulnerability over the Internet.

I visit news servers frequently from my home computer. Does this vulnerability affect me?
No. It only affects servers that offer NNTP services; it does not affect the client systems that visit them.

What does the update do?
The update removes the vulnerability by modifying the way that the NNTP component validates the length of a message before it passes the message to the allocated buffer.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information indicating that this vulnerability had been publicly disclosed when this security bulletin was originally issued.

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

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

/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 about the supported installation switches, see Microsoft Knowledge Base Article 262841.

Deployment Information

To install the security update without any user intervention, use the following command at a command prompt for Windows Server 2003:

Windowsserver2003-kb883935-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-kb883935-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

In some cases, this update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are in use, this update will require a restart. If this occurs, a message appears that advises you to restart.

Removal Information

To remove this update, use the Add or Remove Programs tool in Control Panel.

System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB883935$\Spuninst folder. The Spuninst.exe utility supports the following setup switches:

/?: Show the list of installation switches.

/u: Use unattended mode.

/f: Force other programs to quit when the computer shuts down.

/z: Do not restart when the installation is complete.

/q: Use Quiet mode (no user interaction).

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:

Date Time Version Size File name Folder
-------------------------------------------------------------------------
26-Aug-2004 22:06 6.0.3790.206 139,264 Nntpfs.dll RTMGDR
26-Aug-2004 22:06 6.0.3790.206 565,248 Nntpsvc.dll RTMGDR
27-Aug-2004 02:08 6.0.3790.206 139,264 Nntpfs.dll RTMQFE
27-Aug-2004 02:08 6.0.3790.206 567,296 Nntpsvc.dll RTMQFE

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

Date Time Version Size File name Platform Folder
-------------------------------------------------------------------------
26-Aug-2004 22:08 6.0.3790.206 357,888 Nntpfs.dll IA-64 RTMGDR
26-Aug-2004 22:08 6.0.3790.206 1,654,272 Nntpsvc.dll IA-64 RTMGDR\IA
26-Aug-2004 22:08 6.0.3790.206 1,654,272 Nntpsvc.dll IA-64 RTMGDR\ID
26-Aug-2004 22:08 6.0.3790.206 1,654,272 Nntpsvc.dll IA-64 RTMGDR\IS
27-Aug-2004 02:08 6.0.3790.206 357,888 Nntpfs.dll IA-64 RTMQFE
27-Aug-2004 02:08 6.0.3790.206 1,659,392 Nntpsvc.dll IA-64 RTMQFE\IA
27-Aug-2004 02:08 6.0.3790.206 1,659,392 Nntpsvc.dll IA-64 RTMQFE\ID
27-Aug-2004 02:08 6.0.3790.206 1,659,392 Nntpsvc.dll IA-64 RTMQFE\IS

Note When you install this security update on Windows Server 2003 or on Windows XP 64-Bit Edition Version 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 one of these files, the installer copies the RTMQFE files to your system. Otherwise, the installer copies the RTMGDR files to your system. For more information, see Microsoft Knowledge Base Article 824994.

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

Windows 2000 Server (all versions)

Prerequisites
For Windows 2000 Server, 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 Windows 2000 Server Service Pack 5.

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

/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.

Deployment Information

To install the security update without any user intervention, use the following command at a command prompt for Windows 2000 Server Service Pack 3 and Windows 2000 Server Service Pack 4:

Windows2000-kb883935-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 Server Service Pack 3 and Windows 2000 Server Service Pack 4:

Windows2000-kb883935-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

In some cases, this update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason or if required files are in use, this update will require a restart. If this occurs, a message appears that advises you to restart.

Removal Information

To remove this security update, use the Add or Remove Programs tool in Control Panel.

System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB883935$\Spuninst folder. The Spuninst.exe utility supports the following setup switches:

/?: Show the list of installation switches.

/u: Use unattended mode.

/f: Force other programs to quit when the computer shuts down.

/z: Do not restart when the installation is complete.

/q: Use Quiet mode (no user interaction).

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 Server Service Pack 3 and Windows 2000 Server Service Pack 4:

Date Time Version Size File name
--------------------------------------------------------
26-Aug-2004 21:48 5.0.2195.6972 136,976 Nntpfs.dll
26-Aug-2004 21:48 5.0.2195.6972 613,136 Nntpsvc.dll

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

Windows NT Server 4.0 (all versions)

Prerequisites
This security update requires Windows NT Server 4.0 Service Pack 6a (SP6a).

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:

/x Generates a list of the packaged files. You can select the files that you want to extract and the location.

/s Performs a silent installation. This switch stops services and installs the hotfix with no prompts or user interface (UI). You need to allow sufficient time for the hotfix to be installed, because this switch returns control to the command prompt well before the installation is finished. Verify that the hotfix is installed.

/z The same as the /x switch, but the /z switch automatically restarts the computer. Do not use the /z switch unless you want to automatically restart the computer.

/m Prompts you for the folder locations. You can select the folder locations of the Windows folder, System folder, System32 folder, Temp folder, Source folder (which is usually the Temp folder), System Windows folder, and Language folder.

Note You can combine these switches into one command. For more information about the supported installation switches, see Microsoft Knowledge Base Article 257946.

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:

WindowsNT4OptionPack-KB883935-x86-enu.exe /s

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:

WindowsNT4OptionPack-KB883935-x86-enu.exe /s

For more information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site.

Restart Requirement

In some cases, this update does not require a restart. The installer stops the needed services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason or if required files are in use, this update will require a restart. If this occurs, a message appears that advises you to restart.

Removal Information

To remove this security update, use the Add/Remove Programs tool in Control Panel.

System administrators can issue the following command to remove this security update.
%Windir%\883935\UNINSTALL\UNINST.EXE

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:

Date Time Version Size File name
------------------------------------------------------
03-Sep-2004 21:15 5.5.1877.79 762,128 Nntpsvc.dll

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:

    HKLM\SOFTWARE\Microsoft\Updates\Windows NT 4 Option Pack\NOSP\883935

    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 883935 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, see 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 (October 12, 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