Check Point Advisories

TLS Renegotiation (CVE-2009-3555)

Check Point Reference: SBP-2009-23
Date Published: 22 Nov 2009
Severity: N/A
Last Updated: Thursday 09 January, 2014
Source:
Industry Reference:CVE-2009-3555
Protection Provided by:

Security Gateway
R81, R80, R77, R75, R71, R70, R65

Who is Vulnerable?
Vulnerability Description Transport Layer Security (TLS) and Secure Sockets Layer (SSL) are cryptographic protocols that provide security for communications over networks. A spoofing vulnerability exists in multiple implementations of these protocols. The vulnerability is due to the flaw in the renegotiation aspect of the TLS protocol. A remote attacker may exploit this issue by sending an unauthenticated request that is processed retroactively by a server in a post-renegotiation context. Successful exploitation of this issue may allow the attacker to execute a man-in-the-middle attack. There are cases in which certain traffic, although not intended for malicious use, is very unsafe, since it may transfer shellcode which is undetectable by IPS.

Protection Overview

The TLS Renegotiation protection detects and blocks all TLS renegotiation traffic.The TLS Client Initiated Renegotiation protection detects and blocks client initiated TLS renegotiation requests.

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 / R71 / R70 / R65

  1. In the IPS tab, click Protections and find the TLS Renegotiation 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:  SSL Enforcement Violation.
Attack Information:  TLS renegotiation

×
  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