SOL13167034 - OpenSSL vulnerability CVE-2016-2183

Vulnerability Recommended Actions

If you are running a version listed in the Versions known to be vulnerable column, you can eliminate this vulnerability by upgrading to a version listed in theVersions known to be not vulnerable column. If the table lists only an older version than what you are currently running, or does not list a non-vulnerable version, then no upgrade candidate currently exists.

To determine the necessary upgrade path for your BIG-IQ system, you should understand the BIG-IQ product offering name changes. For more information, refer to SOL21232150: Considerations for upgrading BIG-IQ or F5 iWorkflow systems.

Mitigation

The following mitigation options are available for the BIG-IP system:

SSL profiles

You can mitigate this issue for the SSL profiles by disabling 3DES (DES-CBC3) ciphers for the affected profile. For information about configuring the cipher strength for the SSL profiles, refer to SOL17370: Configuring the cipher strength for SSL profiles (12.x).

Alternatively, if disabling 3DES ciphers is not possible, you can modify the SSL profile and set the Renegotiation Size setting to 1 GB. To do so, perform the following procedure:

1. Log into the Traffic Management Shell (tmsh) utility by typing the following command:

tmsh

2. Change the renegotiation size to 1 GB for the profile using the following command syntax:

modify /ltm profile client-ssl <profile_name> renegotiate-size 1000

For example, the following command changes the renegotiation size to 1 GB for the SSL profile named MyClientSSL:

modify /ltm profile client-ssl MyClientSSL renegotiate-size 1000

3. Save the changes by typing the following command:

save /sys config

Authentication profiles (tamd)

To mitigate this issue, disable 3DES on the server side to prevent negotiation of the vulnerable cipher.

Configuration utility

To mitigate this vulnerability for the BIG-IP Configuration utility, you should permit management access to F5 products only over a secure network. For more information, refer to SOL13092: Overview of securing access to the BIG-IP system.

BIG-IP APM - Oracle Access Manager

To mitigate this vulnerability for the Oracle Access Manager (OAM), you should monitor traffic patterns between BIG-IP system and back-end Oracle Access Manager systems for traffic anomalies, or force rekeying on an appropriate interval on their application server.

Supplemental Information

• SOL9970: Subscribing to email notifications regarding F5 products
• SOL9957: Creating a custom RSS feed to view new and updated documents
• SOL4602: Overview of the F5 security vulnerability response policy
• SOL4918: Overview of the F5 critical issue hotfix policy
• SOL167: Downloading software and firmware from F5
• SOL13123: Managing BIG-IP product hotfixes (11.x - 12.x)
• SOL10025: Managing BIG-IP product hotfixes (10.x)
• SOL9502: BIG-IP hotfix matrix
• SOL15106: Managing BIG-IQ product hotfixes
• SOL15113: BIG-IQ hotfix matrix
• SOL10322: FirePass hotfix matrix
• SOL12766: ARX hotfix matrix