August 9, 2011
The Microsoft .NET Framework is prone to a security-bypass vulnerability. Attackers can exploit this issue to perform denial-of-service attacks, scan network resources, and obtain potentially sensitive information that was not intended to be disclosed.
- Avaya Aura Conferencing 6.0 Standard
- Avaya CallPilot 4.0
- Avaya CallPilot 5.0
- Avaya Communication Server 1000 Telephony Manager 3.0
- Avaya Communication Server 1000 Telephony Manager 4.0
- 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 Meeting Exchange 5.0
- Avaya Meeting Exchange 5.0 SP1
- Avaya Meeting Exchange 5.0 SP2
- Avaya Meeting Exchange 188.8.131.52.52
- Avaya Meeting Exchange 5.1
- Avaya Meeting Exchange 5.1 SP1
- Avaya Meeting Exchange 5.2
- Avaya Meeting Exchange 5.2 SP1
- Avaya Meeting Exchange 5.2 SP2
- Avaya Messaging Application Server 4
- Avaya Messaging Application Server 5
- Avaya Messaging Application Server 5.2
- Microsoft .NET Framework 2.0 SP2
- Microsoft .NET Framework 3.5
- Microsoft .NET Framework 3.5.1
- Microsoft .NET Framework 4.0
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.
Run all software as a nonprivileged user with minimal access rights.
To limit the consequences of a successful exploit, run the application with the least privilege required.
Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to detect and block attacks and anomalous activity such as requests containing suspicious URI sequences. Since the webserver may log such requests, review its logs regularly.
Do not follow links provided by unknown or untrusted sources.
Do not use client software to visit sites of unknown or questionable integrity.
Vendor updates are available. Please see the references for more information.
Michael J. Liu
© 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 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.