October 12, 2010
Microsoft Windows is prone to a local privilege-escalation vulnerability. Attackers may exploit this issue to execute arbitrary code with kernel-level privileges. Successfully exploiting this issue will result in the complete compromise of affected computers. Failed exploit attempts will result in a denial-of-service condition.
- Avaya CallPilot
- Avaya Communication Server 1000 Telephony Manager
- Avaya Meeting Exchange - Client Registration Server
- Avaya Meeting Exchange - Recording Server
- Avaya Meeting Exchange - Streaming Server
- Avaya Meeting Exchange - Web Conferencing Server
- Avaya Meeting Exchange - Webportal
- Avaya Messaging Application Server
- Microsoft Windows Server 2003 Datacenter x64 Edition SP2
- Microsoft Windows Server 2003 Enterprise x64 Edition SP2
- Microsoft Windows Server 2003 Itanium SP2
- Microsoft Windows Server 2003 SP2
- Microsoft Windows Server 2003 Sp2 Compute Cluster
- Microsoft Windows Server 2003 Sp2 Datacenter
- Microsoft Windows Server 2003 Sp2 Enterprise
- Microsoft Windows Server 2003 Sp2 Storage
- Microsoft Windows Server 2003 Standard Edition SP2
- Microsoft Windows Server 2003 Web Edition SP2
- Microsoft Windows Server 2003 x64 SP2
- Microsoft Windows XP Embedded SP3
- Microsoft Windows XP Home SP3
- Microsoft Windows XP Media Center Edition SP3
- Microsoft Windows XP Professional SP3
- Microsoft Windows XP Professional x64 Edition SP2
- Microsoft Windows XP Tablet PC Edition SP3
Permit local access for trusted individuals only. Where possible, use restricted environments and restricted shells.
Allow only trusted and accountable individuals to have local interactive access to vulnerable computers.
Implement multiple redundant layers of security.
As an added precaution, deploy memory-protection schemes (such as nonexecutable stack/heap configuration and randomly mapped memory segments). This may complicate exploits of memory-corruption vulnerabilities.
The vendor released an advisory and updates. Please see the references for details.
Diego Juarez of Core Security Technologies
© 1995- 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 email@example.com.
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 firstname.lastname@example.org 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.