- Date Discovered:
- August 12, 2014
- Microsoft .NET Framework is prone to a security-bypass vulnerability. An attacker can leverage this issue to bypass certain security restrictions and execute arbitrary code by exploiting another vulnerability in the application.
- Avaya Conferencing Standard Edition 6.0
- Avaya Conferencing Standard Edition 6.0 SP1
- Avaya Conferencing Standard Edition 6.0.1
- Avaya Meeting Exchange - Client Registration Server 6.2
- Avaya Meeting Exchange - Recording Server 6.2
- Avaya Meeting Exchange - Streaming Server 6.2
- Avaya Meeting Exchange - Web Conferencing Server 6.2
- Avaya Meeting Exchange - Webportal 6.2
- Microsoft .NET Framework 2.0 SP2
- Microsoft .NET Framework 3.0 SP2
- Microsoft .NET Framework 3.5
- Microsoft .NET Framework 3.5.1
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 exploits.
Run all software as a nonprivileged user with minimal access rights.To reduce the impact of latent vulnerabilities, run the application with the minimal amount of privileges required for functionality.
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 unexplained incoming and outgoing traffic. This may indicate exploit attempts or activity that results from successful exploits.
Implement multiple redundant layers of security.Various memory-protection schemes (such as nonexecutable and randomly mapped memory segments) may hinder an attacker's ability to exploit this vulnerability to execute arbitrary code.