March 13, 2012
Microsoft Windows is prone to a remote denial-of-service vulnerability. Successful exploits will cause the vulnerable applications that use the affected API to crash or become unresponsive, denying service to legitimate users.
- Avaya Aura Conferencing 6.0 SP1 Standard
- Avaya Aura Conferencing 6.0 Standard
- Microsoft Windows Server 2008 R2 Itanium
- Microsoft Windows Server 2008 R2 Itanium SP1
- Microsoft Windows Server 2008 R2 x64
- Microsoft Windows Server 2008 R2 x64 SP1
- Microsoft Windows Server 2008 for 32-bit Systems
- Microsoft Windows Server 2008 for 32-bit Systems SP2
- Microsoft Windows Vista SP1
- Microsoft Windows Vista SP2
- Microsoft Windows Vista x64 Edition SP1
- Microsoft Windows Vista x64 Edition SP2
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 a successful exploit.
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 a successful exploit.
Do not accept or execute files from untrusted or unknown sources.
To reduce the likelihood of successful exploits, never handle files that originate from unfamiliar or untrusted sources.
Do not follow links provided by unknown or untrusted sources.
To reduce the likelihood of successful exploits, never visit sites of questionable integrity or follow links provided by unfamiliar or untrusted sources.
Vendor updates are available. Please see the references for details.
Khaled M. Salameh
© 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.