1. /
  2. Security Response/
  3. Microsoft RPC Runtime Library Remote Denial Of Service And Information Disclosure Vulnerability

Microsoft RPC Runtime Library Remote Denial Of Service And Information Disclosure Vulnerability

Risk

High

Date Discovered

October 12, 2004

Description

Microsoft RPC Runtime Library is affected by a remote denial of service and information disclosure vulnerability. This issue is due to a failure of the library to properly handle exceptional network traffic. An attacker may leverage this issue to disclose potentially sensitive information and to cause the affected application to crash, denying service to legitimate users.

Technologies Affected

  • Avaya DefinityOne Media Servers
  • Avaya DefinityOne Media Servers R10
  • Avaya DefinityOne Media Servers R11
  • Avaya DefinityOne Media Servers R12
  • Avaya DefinityOne Media Servers R6
  • Avaya DefinityOne Media Servers R7
  • Avaya DefinityOne Media Servers R8
  • Avaya DefinityOne Media Servers R9
  • Avaya IP600 Media Servers
  • Avaya IP600 Media Servers R10
  • Avaya IP600 Media Servers R11
  • Avaya IP600 Media Servers R12
  • Avaya IP600 Media Servers R6
  • Avaya IP600 Media Servers R7
  • Avaya IP600 Media Servers R8
  • Avaya IP600 Media Servers R9
  • Avaya Modular Messaging (MSS) 1.1.0
  • Avaya Modular Messaging (MSS) 2.0.0
  • Avaya S3400 Message Application Server
  • Avaya S8100 Media Servers
  • Avaya S8100 Media Servers R10
  • Avaya S8100 Media Servers R11
  • Avaya S8100 Media Servers R12
  • Avaya S8100 Media Servers R6
  • Avaya S8100 Media Servers R7
  • Avaya S8100 Media Servers R8
  • Avaya S8100 Media Servers R9
  • Microsoft Windows 98SE
  • Microsoft Windows ME
  • Microsoft Windows NT 4.0
  • Microsoft Windows NT 4.0 SP1
  • Microsoft Windows NT 4.0 SP1 alpha
  • Microsoft Windows NT 4.0 SP2
  • Microsoft Windows NT 4.0 SP2 alpha
  • Microsoft Windows NT 4.0 SP3
  • Microsoft Windows NT 4.0 SP3 alpha
  • Microsoft Windows NT 4.0 SP4
  • Microsoft Windows NT 4.0 SP4 alpha
  • Microsoft Windows NT 4.0 SP5
  • Microsoft Windows NT 4.0 SP5 alpha
  • Microsoft Windows NT 4.0 SP6
  • Microsoft Windows NT 4.0 SP6 alpha
  • Microsoft Windows NT 4.0 SP6a
  • Microsoft Windows NT 4.0 SP6a alpha
  • Microsoft Windows NT 4.0 alpha
  • Microsoft Windows NT Enterprise Server 4.0
  • Microsoft Windows NT Enterprise Server 4.0 SP1
  • Microsoft Windows NT Enterprise Server 4.0 SP2
  • Microsoft Windows NT Enterprise Server 4.0 SP3
  • Microsoft Windows NT Enterprise Server 4.0 SP4
  • Microsoft Windows NT Enterprise Server 4.0 SP5
  • Microsoft Windows NT Enterprise Server 4.0 SP6
  • Microsoft Windows NT Enterprise Server 4.0 SP6a
  • Microsoft Windows NT Server 4.0
  • Microsoft Windows NT Server 4.0 SP1
  • Microsoft Windows NT Server 4.0 SP2
  • Microsoft Windows NT Server 4.0 SP3
  • Microsoft Windows NT Server 4.0 SP4
  • Microsoft Windows NT Server 4.0 SP5
  • Microsoft Windows NT Server 4.0 SP6
  • Microsoft Windows NT Server 4.0 SP6a
  • Microsoft Windows NT Terminal Server 4.0
  • Microsoft Windows NT Terminal Server 4.0 SP1
  • Microsoft Windows NT Terminal Server 4.0 SP2
  • Microsoft Windows NT Terminal Server 4.0 SP3
  • Microsoft Windows NT Terminal Server 4.0 SP4
  • Microsoft Windows NT Terminal Server 4.0 SP5
  • Microsoft Windows NT Terminal Server 4.0 SP6
  • Microsoft Windows NT Terminal Server 4.0 SP6a
  • Microsoft Windows NT Terminal Server 4.0 alpha
  • Microsoft Windows NT Workstation 4.0
  • Microsoft Windows NT Workstation 4.0 SP1
  • Microsoft Windows NT Workstation 4.0 SP2
  • Microsoft Windows NT Workstation 4.0 SP3
  • Microsoft Windows NT Workstation 4.0 SP4
  • Microsoft Windows NT Workstation 4.0 SP5
  • Microsoft Windows NT Workstation 4.0 SP6
  • Microsoft Windows NT Workstation 4.0 SP6a

Recommendations

Block external access at the network boundary, unless external parties require service.

Filter access to all ports related to the service such as UDP 135-138. and 455 as well as TCP 135, 139, 445 and 593. Ports above 1024 should also be filtered if not required in addition to any other RPC related ports. CIS or RPC over HTTP should also be filtered through ports 80 and 443.

Deploy network intrusion detection systems to monitor network traffic for malicious activity.

Deploy network intrusion detection systems to monitor all network traffic for signs of suspicious or anomalous activity. This may aid in detecting attempts to exploit latent vulnerabilities or in detecting malicious activity that occurs as a result of successful exploitation.
Avaya has released an advisory that acknowledges this vulnerability for Avaya products. Customers are advised to follow Microsoft's guidance for applying patches. Please see the referenced Avaya advisory at the following location for further details: http://support.avaya.com/japple/css/japple?temp.groupID=128450&temp.selectedFamily=128451&temp.selectedProduct=154235&temp.selectedBucket=126655&temp.feedbackState=askForFeedback&temp.documentID=203487&PAGE=avaya.css.CSSLvl1Detail&executeTransaction=avaya.css.UsageUpdate() Microsoft has released a bulletin that includes fixes to address this issue for supported versions of the operating system.

Credits

The individual responsible for the discovery of this issue is currently unknown; BindView Corporation is credited with disclosure.
Copyright © Symantec Corporation.
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from secure@symantec.com.

Disclaimer
The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Security Response, and secure@symantec.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.

Threat Intelligence

Subscribe
Follow the Threat Intelligence Twitter feed
STAR Antimalware Protection Technologies
Internet Security Threat Report
Symantec DeepSight Screensaver