Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4
Fixed In:
12.1.0, 11.6.2, 11.5.5
Opened: Sep 10, 2015 Severity: 3-Major
There is no limit to the number of active SSL handshakes on one BIG-IP system. With many calls, memory can be exhausted and cause system problems.
The memory and/or CPU can be exhausted.
When the BIG-IP system has too many active SSL handshakes.
None.
Added limitation for active SSL handshakes to prevent CPU and memory exhaustion. There is a new db variable 'tmm.ssl.maxactivehandshakes' that limits the total number of active SSL handshakes. By default this variable is set to '0', which means no limit.
There is a new db variable 'tmm.ssl.maxactivehandshakes', which limits the total number of active SSL handshakes. By default this variable is set to '0', which means no limit.