Last Modified: Jul 18, 2026
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.