On version 16.1.x before 16.1.2, 15.1.x before 15.1.4.1, 14.1.x before 14.1.4.5, and all versions of 13.1.x, when the BIG-IP Virtual Edition (VE) uses the ixlv driver (which is used in SR-IOV mode and requires Intel X710/XL710/XXV710 family of network adapters on the Hypervisor) and TCP Segmentation Offload configuration is enabled, undisclosed requests may cause an increase in CPU 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 | 13.1.0 (including) | 13.1.4 (including) |
Big-ip_access_policy_manager | F5 | 14.1.0 (including) | 14.1.4 (including) |
Big-ip_access_policy_manager | F5 | 15.1.0 (including) | 15.1.4 (including) |
Big-ip_access_policy_manager | F5 | 16.1.0 (including) | 16.1.1 (including) |
Big-ip_advanced_firewall_manager | F5 | 13.1.0 (including) | 13.1.4 (including) |
Big-ip_advanced_firewall_manager | F5 | 14.1.0 (including) | 14.1.4 (including) |
Big-ip_advanced_firewall_manager | F5 | 15.1.0 (including) | 15.1.4 (including) |
Big-ip_advanced_firewall_manager | F5 | 16.1.0 (including) | 16.1.1 (including) |
Big-ip_advanced_web_application_firewall | F5 | 13.1.0 (including) | 13.1.4 (including) |
Big-ip_advanced_web_application_firewall | F5 | 14.1.0 (including) | 14.1.4 (including) |
Big-ip_advanced_web_application_firewall | F5 | 15.1.0 (including) | 15.1.4 (including) |
Big-ip_advanced_web_application_firewall | F5 | 16.1.0 (including) | 16.1.1 (including) |
Big-ip_analytics | F5 | 13.1.0 (including) | 13.1.4 (including) |
Big-ip_analytics | F5 | 14.1.0 (including) | 14.1.4 (including) |
Big-ip_analytics | F5 | 15.1.0 (including) | 15.1.4 (including) |
Big-ip_analytics | F5 | 16.1.0 (including) | 16.1.1 (including) |
Big-ip_application_acceleration_manager | F5 | 13.1.0 (including) | 13.1.4 (including) |
Big-ip_application_acceleration_manager | F5 | 14.1.0 (including) | 14.1.4 (including) |
Big-ip_application_acceleration_manager | F5 | 15.1.0 (including) | 15.1.4 (including) |
Big-ip_application_acceleration_manager | F5 | 16.1.0 (including) | 16.1.1 (including) |
Big-ip_application_security_manager | F5 | 13.1.0 (including) | 13.1.4 (including) |
Big-ip_application_security_manager | F5 | 14.1.0 (including) | 14.1.4 (including) |
Big-ip_application_security_manager | F5 | 15.1.0 (including) | 15.1.4 (including) |
Big-ip_application_security_manager | F5 | 16.1.0 (including) | 16.1.1 (including) |
Big-ip_ddos_hybrid_defender | F5 | 13.1.0 (including) | 13.1.4 (including) |
Big-ip_ddos_hybrid_defender | F5 | 14.1.0 (including) | 14.1.4 (including) |
Big-ip_ddos_hybrid_defender | F5 | 15.1.0 (including) | 15.1.4 (including) |
Big-ip_ddos_hybrid_defender | F5 | 16.1.0 (including) | 16.1.1 (including) |
Big-ip_domain_name_system | F5 | 13.1.0 (including) | 13.1.4 (including) |
Big-ip_domain_name_system | F5 | 14.1.0 (including) | 14.1.4 (including) |
Big-ip_domain_name_system | F5 | 15.1.0 (including) | 15.1.4 (including) |
Big-ip_domain_name_system | F5 | 16.1.0 (including) | 16.1.1 (including) |
Big-ip_fraud_protection_service | F5 | 13.1.0 (including) | 13.1.4 (including) |
Big-ip_fraud_protection_service | F5 | 14.1.0 (including) | 14.1.4 (including) |
Big-ip_fraud_protection_service | F5 | 15.1.0 (including) | 15.1.4 (including) |
Big-ip_fraud_protection_service | F5 | 16.1.0 (including) | 16.1.1 (including) |
Big-ip_global_traffic_manager | F5 | 13.1.0 (including) | 13.1.4 (including) |
Big-ip_global_traffic_manager | F5 | 14.1.0 (including) | 14.1.4 (including) |
Big-ip_global_traffic_manager | F5 | 15.1.0 (including) | 15.1.4 (including) |
Big-ip_global_traffic_manager | F5 | 16.1.0 (including) | 16.1.1 (including) |
Big-ip_link_controller | F5 | 13.1.0 (including) | 13.1.4 (including) |
Big-ip_link_controller | F5 | 14.1.0 (including) | 14.1.4 (including) |
Big-ip_link_controller | F5 | 15.1.0 (including) | 15.1.4 (including) |
Big-ip_link_controller | F5 | 16.1.0 (including) | 16.1.1 (including) |
Big-ip_local_traffic_manager | F5 | 13.1.0 (including) | 13.1.4 (including) |
Big-ip_local_traffic_manager | F5 | 14.1.0 (including) | 14.1.4 (including) |
Big-ip_local_traffic_manager | F5 | 15.1.0 (including) | 15.1.4 (including) |
Big-ip_local_traffic_manager | F5 | 16.1.0 (including) | 16.1.1 (including) |
Big-ip_policy_enforcement_manager | F5 | 13.1.0 (including) | 13.1.4 (including) |
Big-ip_policy_enforcement_manager | F5 | 14.1.0 (including) | 14.1.4 (including) |
Big-ip_policy_enforcement_manager | F5 | 15.1.0 (including) | 15.1.4 (including) |
Big-ip_policy_enforcement_manager | F5 | 16.1.0 (including) | 16.1.1 (including) |
Big-ip_ssl_orchestrator | F5 | 13.1.0 (including) | 13.1.4 (including) |
Big-ip_ssl_orchestrator | F5 | 14.1.0 (including) | 14.1.4 (including) |
Big-ip_ssl_orchestrator | F5 | 15.1.0 (including) | 15.1.4 (including) |
Big-ip_ssl_orchestrator | F5 | 16.1.0 (including) | 16.1.1 (including) |
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.