Horizon Alert
Summary of the vulnerability and why it matters
A critical vulnerability has been identified in a specific configuration of BIG-IP virtual servers, where undisclosed requests can cause a system process to terminate, potentially leading to disruption and unauthorized code execution. This issue is a data plane concern, meaning it directly impacts traffic handling rather than administrative access.
- System process termination impacts traffic delivery.
- Allows remote attackers to disrupt services.
- Confirm relevance and exposure to this configuration.
Attack Path
How an attacker could exploit the issue
An attacker can reach the vulnerable component by sending specific, undisclosed requests over the network to a BIG-IP system. This is possible when the system is configured with an HTTP profile and an iRule that uses the MR::message route command. Successful exploitation can cause a denial-of-service and potentially lead to remote code execution.
- Network access required for attack.
- Special HTTP requests trigger vulnerability.
- System crash, potential code execution.
Live Threat
Current exploitation, exposure, and threat context
When an HTTP profile and an iRule using the MR::message route command are configured, certain requests could cause the Traffic Management Microkernel (TMM) to terminate. This vulnerability is a data plane issue only and does not expose the control plane.
- System traffic disruption is possible.
- Undisclosed requests may trigger TMM termination.
- Remote code execution is a potential outcome.
Operational Fix
Recommended remediation, mitigation, and detection steps
The BIG-IP platform team or the infrastructure team responsible for network traffic management is likely to own this vulnerability. The first practical step is to identify all BIG-IP virtual servers with HTTP profiles and iRules using the MR::message route command, then determine their business criticality and external reachability. Planning remediation should be based on this risk assessment, which may involve coordination with the vendor if a fix is available and requires specific deployment.
- Identify BIG-IP instances with HTTP profiles and iRules.
- Confirm external reachability and business criticality.
- Plan risk-based remediation and vendor coordination.