Check Point Advisories

OpenSSL ssl3_get_key_exchange Use-After-Free Memory Corruption (CVE-2010-2939)

Check Point Reference: CPAI-2010-355
Date Published: 16 Sep 2010
Severity: High
Last Updated: Monday 20 November, 2017
Source:
Industry Reference:CVE-2010-2939
Protection Provided by:

Security Gateway
R81, R80, R77, R75

Who is Vulnerable?
Vulnerability Description OpenSSL is an open-source library that implements Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocol functionality. A memory corruption vulnerability has been reported in OpenSSL library. The vulnerability is due to an error in ssl3_get_key_exchange function while handling server key exchange message. If a certificate structure contains a crafted value, the vulnerable code could cause a double-free error. A remote attacker could exploit this issue by enticing the target user to connect to a malicious server using a vulnerable version of the OpenSSL library. Successful exploitation of this vulnerability may allow arbitrary code execution with the privileges of the application using the OpenSSL library.

Protection Overview

This protection will detect and block attempts to exploit this vulnerability.

In order for the protection to be activated, update your Security Gateway product to the latest IPS update. For information on how to update IPS, go to SBP-2006-05, click on Protection tab and select the version of your choice.

Security Gateway R80 / R77 / R75

  1. In the IPS tab, click Protections and find the OpenSSL ssl3_get_key_exchange Use-After-Free Memory Corruption protection using the Search tool and Edit the protection's settings.
  2. Install policy on all Security Gateways.

This protection's log will contain the following information:

Attack Name:  OpenSSL Enforcement Violation.
Attack Information:  OpenSSL ssl3_get_key_exchange Use-After-Free Memory Corruption

×
  Feedback
This website uses cookies for its functionality and for analytics and marketing purposes. By continuing to use this website, you agree to the use of cookies. For more information, please read our Cookies Notice.
OK