1. /
  2. Security Response/
  3. Microsoft Windows Plug And Play UMPNPMGR.DLL wsprintfW Buffer Overflow Vulnerability

Microsoft Windows Plug And Play UMPNPMGR.DLL wsprintfW Buffer Overflow Vulnerability

Risk

High

Date Discovered

October 11, 2005

Description

Microsoft Windows Plug and Play is prone to a buffer overflow vulnerability. This issue is due to a failure of the service to properly bounds check user-supplied data prior to copying it to an insufficiently sized memory buffer. This issue takes place when the PnP service handles malformed messages containing excessive data. This vulnerability facilitates local privilege escalation and unauthorized remote access depending on the underlying operating system. A successful attack may result in arbitrary code execution resulting in an attacker gaining SYSTEM privileges. This issue is unrelated to the one documented in BID 14513, "Microsoft Windows Plug and Play Buffer Overflow Vulnerability", but they both have similar attack scenarios and affects.

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 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
  • Avaya Unified Communication Center
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Advanced Server SP1
  • Microsoft Windows 2000 Advanced Server SP2
  • Microsoft Windows 2000 Advanced Server SP3
  • Microsoft Windows 2000 Advanced Server SP4
  • Microsoft Windows 2000 Datacenter Server
  • Microsoft Windows 2000 Datacenter Server SP1
  • Microsoft Windows 2000 Datacenter Server SP2
  • Microsoft Windows 2000 Datacenter Server SP3
  • Microsoft Windows 2000 Datacenter Server SP4
  • Microsoft Windows 2000 Professional
  • Microsoft Windows 2000 Professional SP1
  • Microsoft Windows 2000 Professional SP2
  • Microsoft Windows 2000 Professional SP3
  • Microsoft Windows 2000 Professional SP4
  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Server SP1
  • Microsoft Windows 2000 Server SP2
  • Microsoft Windows 2000 Server SP3
  • Microsoft Windows 2000 Server SP4
  • 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 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
  • Microsoft Windows XP Home
  • Microsoft Windows XP Home SP1
  • Microsoft Windows XP Home SP2
  • Microsoft Windows XP Media Center Edition
  • Microsoft Windows XP Media Center Edition SP1
  • Microsoft Windows XP Media Center Edition SP2
  • Microsoft Windows XP Professional
  • Microsoft Windows XP Professional SP1
  • Microsoft Windows XP Professional SP2
  • Nortel Networks Centrex IP Client Manager
  • Nortel Networks Centrex IP Client Manager 2.5.0
  • Nortel Networks Centrex IP Client Manager 7.0.0
  • Nortel Networks Centrex IP Client Manager 8.0.0
  • Nortel Networks Centrex IP Element Manager 2.5.0
  • Nortel Networks Centrex IP Element Manager 7.0.0
  • Nortel Networks Centrex IP Element Manager 8.0.0

Recommendations

Permit local access for trusted individuals only. Where possible, use restricted environments and restricted shells.

Due to the possibility of local attacks against some affected operating systems, ensure that trusted users have local interactive access to vulnerable computers.

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

Allow network access to affected computers from only trusted hosts and networks. TCP ports 139 and 445 should be restricted at the network perimeter.

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

Network intrusion detection systems should be deployed to monitor network traffic for signs of anomalous or suspicious activity. This includes but is not limited to requests that include NOP sleds and unexplained incoming and outgoing traffic. This may indicate exploitation attempts or activity that results from successful exploitation.

Implement multiple redundant layers of security.

As it may be possible that this issue will be leveraged to execute code, memory protection schemes are recommended. Memory protection schemes such as non-executable stack/heap configurations and randomly mapped memory segments will complicate exploitation of memory corruption vulnerabilities.

Change default user IDs and passwords.

A workaround against the Guest account attack vector is to change the default password for the guest account. This will prevent attackers from connecting to the service and authenticating as Guest.

Review and adjust according to policy any default configuration settings.

Ensure the Guest Account is on the "Deny access to this computer from the network" entry in the "User Rights Assignment" Security Policy. This is the default setting, however enabling file sharing may remove this entry from the policy.

Review and adjust according to policy any default configuration settings.

While file sharing is not enabled by default, administrators should still check to ensure that it is disabled. This is only necessary for systems that are not already patched with the MS05-039 fix or have XP SP2 installed. Such systems are not vulnerable to the Guest account attack vector.
Avaya has released advisory ASA-2005-214 to state which Avaya products are affected by The October 2005 release of Microsoft Windows security updates. Please see the referenced advisory for further information. Nortel Networks has released a technical support bulletin (2005006318) regarding this and other issues for their Centrex IP Client Manager (CICM). They report the vulnerabilities will be fixed in the upcoming 2.5, 7.0 and 8.0 maintenance releases. Please see the referenced bulletin for further information. Fixes are available:

Credits

Derek Soeder discovered this vulnerability.
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