April 10, 2007
Microsoft Windows is prone to a remote stack-based buffer-overflow vulnerability because it fails to adequately bounds-check user-supplied data before copying it to an insufficiently sized memory buffer. This occurs when handling certain HTTP requests.
To exploit this issue, an attacker must be in the same network segment as the victim.
Successful exploits may allow attackers to execute arbitrary code with the privileges of the affected service. Failed exploits attempts will likely result in denial-of-service conditions.
- Avaya Agent Access
- Avaya Basic Call Management System Reporting Desktop
- Avaya Basic Call Management System Reporting Desktop server
- Avaya CMS Supervisor
- Avaya CVLAN
- Avaya Computer Telephony
- Avaya Contact Center Express
- Avaya Customer Interaction Express (CIE) Server 1.0
- Avaya Customer Interaction Express (CIE) User Interface 1.0
- Avaya Enterprise Management
- Avaya IP Agent
- Avaya IP Softphone
- Avaya Integrated Management
- Avaya Interaction Center
- Avaya Interaction Center - Voice Quick Start
- Avaya Modular Messaging (MAS)
- Avaya Network Reporting
- Avaya OctelAccess(r) Server
- Avaya OctelDesignerTM
- Avaya Operational Analyst
- Avaya Outbound Contact Management
- Avaya Speech Access
- Avaya Unified Communication Center
- Avaya Unified Communications Center S3400
- Avaya VPNmanagerTM Console
- Avaya Visual Messenger TM
- Avaya Visual Vector Client
- Avaya Web Messenger
- Microsoft Windows XP
- 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
- Microsoft Windows XP Professional x64 Edition
- Microsoft Windows XP Professional x64 Edition SP2
- Microsoft Windows XP Tablet PC Edition
- Microsoft Windows XP Tablet PC Edition SP1
- Microsoft Windows XP Tablet PC Edition SP2
- Nortel Networks Enterprise NMS
- Nortel Networks Multiservice Data Manager (Operator Client)
Block external access at the network boundary, unless external parties require service.
If global access isn't needed, filter access to the affected computer at the network boundary. Restricting access to only trusted computers and
networks might greatly reduce the likelihood of successful exploits.
Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS 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 exploit attempts or activity that results from successful exploits.
Implement multiple redundant layers of security.
Memory-protection schemes such as non-executable stack/heap configurations and randomly mapped memory segments will reduce the likelihood of memory-corruption exploits.
The vendor released fixes to address this issue. Please see the references for more information.
Greg MacManus working with iDefense Labs is credited with the discovery of this issue.
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 firstname.lastname@example.org
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 email@example.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.