F5 BIG-IP family denial of service and possible RCE in MR::message routing
F5 BIG-IP · F5 BIG-IP Next for Kubernetes
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| F5 BIG-IP |
| No fix yet |
| F5 BIG-IP Next for Kubernetes |
| No fix yet |
F5 BIG-IP · F5 BIG-IP Next for Kubernetes
| Product | Affected | Fixed in |
|---|---|---|
| F5 BIG-IP |
| No fix yet |
| F5 BIG-IP Next for Kubernetes |
| No fix yet |
Description:
When an HTTP profile and an iRule using the
MR::message
route command are configured on a virtual server, undisclosed requests can cause the Traffic Management Microkernel (TMM) to terminate and may lead to remote code execution (RCE)
Impact:
Traffic is disrupted while the TMM process restarts. This vulnerability allows a remote, unauthenticated attacker to cause a denial-of-service (DoS) on the BIG-IP system and may allow the attacker to perform RCE. There is no control plane exposure; this is a data plane issue only.
Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
From the CVE record · f5
A virtual server configured with an HTTP profile and an iRule using the MR::message route command is vulnerable to requests that can terminate the Traffic Management Microkernel (TMM). A remote, unauthenticated attacker can disrupt traffic while TMM restarts and may be able to execute code. This is a data-plane issue, with no control-plane exposure.
Operators of F5 BIG-IP or F5 BIG-IP Next for Kubernetes should check virtual servers with this configuration; affected versions were not provided.