Horizon Alert
Summary of the vulnerability and why it matters
A critical vulnerability exists in F5 BIG-IP systems when specific traffic processing rules are enabled. This issue can disrupt traffic and potentially allow attackers to execute code remotely, impacting the availability of services managed by these systems. The main concern is confirming relevance and exposure to understand the potential impact on our environment.
- Client traffic rules can crash system.
- Remote attackers may gain code execution.
- Confirm if our systems are impacted.
Attack Path
How an attacker could exploit the issue
An attacker could exploit this vulnerability by sending specially crafted network requests to a BIG-IP system configured with a specific iRule. These requests would target the Traffic Management Microkernel (TMM) via the DNS::scrape command, potentially causing it to crash and leading to remote code execution.
- No authentication or user interaction needed.
- Crafted requests trigger TMM crash.
- Leads to denial-of-service and RCE.
Live Threat
Current exploitation, exposure, and threat context
When an iRule on a BIG-IP virtual server uses the DNS::scrape command, specific requests could cause the Traffic Management Microkernel (TMM) to terminate, potentially allowing remote code execution and disrupting traffic.
- System processes could terminate unexpectedly.
- Undisclosed requests may trigger TMM failure.
- Remote code execution is a potential outcome.
Operational Fix
Recommended remediation, mitigation, and detection steps
This vulnerability impacts F5 BIG-IP systems when specific iRules are configured, potentially leading to DoS and RCE. The first practical step is for infrastructure and security teams to identify all BIG-IP systems, confirm the presence of the vulnerable iRule configuration, and assess their exposure to external traffic. Once identified, the accountable owner should be confirmed, and a risk-based remediation plan, considering maintenance windows and vendor coordination, should be developed.
- Infrastructure and Security teams own the issue.
- Verify BIG-IP systems with vulnerable iRules.
- Plan remediation based on confirmed exposure.