Horizon Alert
Summary of the vulnerability and why it matters
This advisory concerns a critical vulnerability in BIG-IP APM, a technology used for managing access and security policies for network traffic. The issue could allow unauthorized remote attackers to disrupt services or potentially execute code on affected systems. The primary concern is confirming if this specific technology is in use and if it is exposed to potential threats.
- A critical flaw allows remote code execution.
- It impacts network access management systems.
- Confirm relevance and exposure immediately.
Attack Path
How an attacker could exploit the issue
An attacker can exploit this vulnerability by sending specific, undisclosed requests to a BIG-IP system that has APM provisioned and configured with a per-request policy. This policy must include both the Client Information and Endpoint Security agents. The vulnerability lies within the Traffic Management Microkernel (TMM) and, when triggered, can lead to TMM termination and potentially remote code execution.
- Unauthenticated network requests.
- Triggered by specific APM policy requests.
- Denial-of-service, potential RCE.
Live Threat
Current exploitation, exposure, and threat context
When BIG-IP APM is configured with specific policies, undisclosed requests could cause the Traffic Management Microkernel (TMM) to terminate. This may lead to a denial-of-service condition and potentially remote code execution, affecting the availability and integrity of the BIG-IP system's data plane.
- System availability and integrity.
- Undisclosed requests could trigger TMM termination.
- Denial-of-service and potential remote code execution.
Operational Fix
Recommended remediation, mitigation, and detection steps
This critical vulnerability in BIG-IP APM, impacting the Traffic Management Microkernel (TMM), requires immediate attention from F5 BIG-IP administrators and the security operations team responsible for network edge devices. The first practical step involves identifying all BIG-IP APM instances, confirming their exposure to the internet or untrusted networks, and assessing the business criticality of affected virtual servers. Once identified and prioritized, a coordinated plan with the infrastructure or platform team should be established to address the issue, considering potential vendor coordination and maintenance windows.
- Infrastructure/Platform team owns remediation.
- Verify external reachability and asset criticality.
- Plan and execute vendor-recommended fix.