On BIG-IP versions 16.x before 16.1.0, 15.1.x before 15.1.4.1, and 14.1.2.6-14.1.4.4, when a Client SSL profile is configured on a virtual server with Client Certificate Authentication set to request/require and Session Ticket enabled and configured, processing SSL traffic can cause an increase in memory resource utilization. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
The product does not properly control the allocation and maintenance of a limited resource.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Big-ip_access_policy_manager | F5 | 14.1.2.6 (including) | 14.1.4.4 (excluding) |
Big-ip_access_policy_manager | F5 | 15.1.0 (including) | 15.1.4.1 (excluding) |
Big-ip_access_policy_manager | F5 | 16.0.0 (including) | 16.1.0 (excluding) |
Big-ip_advanced_firewall_manager | F5 | 14.1.2.6 (including) | 14.1.4.4 (excluding) |
Big-ip_advanced_firewall_manager | F5 | 15.1.0 (including) | 15.1.4.1 (excluding) |
Big-ip_advanced_firewall_manager | F5 | 16.0.0 (including) | 16.1.0 (excluding) |
Big-ip_analytics | F5 | 14.1.2.6 (including) | 14.1.4.4 (excluding) |
Big-ip_analytics | F5 | 15.1.0 (including) | 15.1.4.1 (excluding) |
Big-ip_analytics | F5 | 16.0.0 (including) | 16.1.0 (excluding) |
Big-ip_application_acceleration_manager | F5 | 14.1.2.6 (including) | 14.1.4.4 (excluding) |
Big-ip_application_acceleration_manager | F5 | 15.1.0 (including) | 15.1.4.1 (excluding) |
Big-ip_application_acceleration_manager | F5 | 16.0.0 (including) | 16.1.0 (excluding) |
Big-ip_application_security_manager | F5 | 14.1.2.6 (including) | 14.1.4.4 (excluding) |
Big-ip_application_security_manager | F5 | 15.1.0 (including) | 15.1.4.1 (excluding) |
Big-ip_application_security_manager | F5 | 16.0.0 (including) | 16.1.0 (excluding) |
Big-ip_domain_name_system | F5 | 14.1.2.6 (including) | 14.1.4.4 (excluding) |
Big-ip_domain_name_system | F5 | 15.1.0 (including) | 15.1.4.1 (excluding) |
Big-ip_domain_name_system | F5 | 16.0.0 (including) | 16.1.0 (excluding) |
Big-ip_fraud_protection_service | F5 | 14.1.2.6 (including) | 14.1.4.4 (excluding) |
Big-ip_fraud_protection_service | F5 | 15.1.0 (including) | 15.1.4.1 (excluding) |
Big-ip_fraud_protection_service | F5 | 16.0.0 (including) | 16.1.0 (excluding) |
Big-ip_global_traffic_manager | F5 | 14.1.2.6 (including) | 14.1.4.4 (excluding) |
Big-ip_global_traffic_manager | F5 | 15.1.0 (including) | 15.1.4.1 (excluding) |
Big-ip_global_traffic_manager | F5 | 16.0.0 (including) | 16.1.0 (excluding) |
Big-ip_link_controller | F5 | 14.1.2.6 (including) | 14.1.4.4 (excluding) |
Big-ip_link_controller | F5 | 15.1.0 (including) | 15.1.4.1 (excluding) |
Big-ip_link_controller | F5 | 16.0.0 (including) | 16.1.0 (excluding) |
Big-ip_local_traffic_manager | F5 | 14.1.2.6 (including) | 14.1.4.4 (excluding) |
Big-ip_local_traffic_manager | F5 | 15.1.0 (including) | 15.1.4.1 (excluding) |
Big-ip_local_traffic_manager | F5 | 16.0.0 (including) | 16.1.0 (excluding) |
Big-ip_policy_enforcement_manager | F5 | 14.1.2.6 (including) | 14.1.4.4 (excluding) |
Big-ip_policy_enforcement_manager | F5 | 15.1.0 (including) | 15.1.4.1 (excluding) |
Big-ip_policy_enforcement_manager | F5 | 16.0.0 (including) | 16.1.0 (excluding) |
Mitigation of resource exhaustion attacks requires that the target system either:
The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.
The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.