Birthday attacks against TLS ciphers with 64bit block size vulnerability (Sweet32)

What is Birthday Attack against TLS ciphers?

When CBC mode of encryption is used, there is simple birthday attack in which after 2^n/2 blocks of data are encrypted with the same key, a collision between two ciphers blocks are expected. A collision in the output would mean that the input is same. This data combined with several conditions (discussed below) can be used to extract plain text of the encrypted data.

Summary of the Vulnerability:
Birthday attacks against TLS ciphers with 64bit block size vulnerability (Sweet32)

Threat
Legacy block ciphers having a block size of 64 bits are vulnerable to a practical collision attack when used in CBC mode. All versions of SSL/TLS protocol support cipher suites that use DES, 3DES, IDEA, or RC2 as the symmetric encryption cipher are affected.
Note: This CVE is patched at following versions
OPENSSL-0.9.8J-0.102.2
LIBOPENSSL0_9_8-0.9.8J-0.102.2
LIBOPENSSL0_9_8-32BIT-0.9.8J-0.102.2
OPENSSL1-1.0.1G-0.52.1
OPENSSL1-DOC-1.0.1G-0.52.1
LIBOPENSSL1_0_0-1.0.1G-0.52.1
LIBOPENSSL1-DEVEL-1.0.1G-0.52.1
JAVA-1_6_0-IBM-1.6.0_SR16.41-81.1
Remediation notes
Disable and stop using DES, 3DES, IDEA, or RC2 ciphers.

Steps to Fix the Vulnerability:

We will be disabling the Vulnerability from the JRE level so that it is blocked on the Application level. The changes are only involved in java.security file and it will block the ciphers. Changing in the server.xml level shall not be needed once done on JRE level.

1. Download the attached java.security file.
2. Shut Down Adeptia Connect services.
3. Go to ".\AdeptiaConnect\ConnectPortal\jre\lib\security" take backup of existing java.security file and use the one downloaded in Step1.
4. Perform the same steps on the Connect Server side by going to ".\AdeptiaConnect\ConnectServer\jre\lib\security" and take backup of existing java.security file and use the one attached below.
5. After making the above changes start the Connect Services.

Changes present in the java.security file

1. Included 3DES_EDE_CBC algorithm in jdk.tls.disabledAlgorithms on line number 651.
2. Removed 3DES_EDE_CBC algorithm from jdk.tls.legacyAlgorithms from line number 708.