The default configuration of the IPsec IKE peer listener in F5 BIG-IP LTM, Analytics, APM, ASM, and Link Controller 11.2.1 before HF16, 11.4.x, 11.5.x before 11.5.4 HF2, 11.6.x before 11.6.1, and 12.x before 12.0.0 HF2; BIG-IP AAM, AFM, and PEM 11.4.x, 11.5.x before 11.5.4 HF2, 11.6.x before 11.6.1, and 12.x before 12.0.0 HF2; BIG-IP DNS 12.x before 12.0.0 HF2; BIG-IP Edge Gateway, WebAccelerator, and WOM 11.2.1 before HF16; BIG-IP GTM 11.2.1 before HF16, 11.4.x, 11.5.x before 11.5.4 HF2, and 11.6.x before 11.6.1; and BIG-IP PSM 11.4.0 through 11.4.1 improperly enables the anonymous IPsec IKE peer configuration object, which allows remote attackers to establish an IKE Phase 1 negotiation and possibly conduct brute-force attacks against Phase 2 negotiations via unspecified vectors.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Big-ip_application_acceleration_manager | F5 | 11.4.0 (including) | 11.4.0 (including) |
| Big-ip_application_acceleration_manager | F5 | 11.4.1 (including) | 11.4.1 (including) |
| Big-ip_application_acceleration_manager | F5 | 11.5.0 (including) | 11.5.0 (including) |
| Big-ip_application_acceleration_manager | F5 | 11.5.1 (including) | 11.5.1 (including) |
| Big-ip_application_acceleration_manager | F5 | 11.5.2 (including) | 11.5.2 (including) |
| Big-ip_application_acceleration_manager | F5 | 11.5.3 (including) | 11.5.3 (including) |
| Big-ip_application_acceleration_manager | F5 | 11.5.4 (including) | 11.5.4 (including) |
| Big-ip_application_acceleration_manager | F5 | 11.6.0 (including) | 11.6.0 (including) |
| Big-ip_application_acceleration_manager | F5 | 12.0.0 (including) | 12.0.0 (including) |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: