TMM Vulnerability
F5 BIG-IP Next SPK · F5 BIG-IP Next CNF · F5 BIG-IP Next for Kubernetes
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| F5 BIG-IP Next SPK |
|
|
| F5 BIG-IP Next CNF |
|
|
| F5 BIG-IP Next for Kubernetes |
| No fix yet |
F5 BIG-IP Next SPK · F5 BIG-IP Next CNF · F5 BIG-IP Next for Kubernetes
| Product | Affected | Fixed in |
|---|---|---|
| F5 BIG-IP Next SPK |
|
|
| F5 BIG-IP Next CNF |
|
|
| F5 BIG-IP Next for Kubernetes |
| No fix yet |
When an iRule is configured on a virtual server via the declarative API, upon re-instantiation, the cleanup process can cause an increase in the Traffic Management Microkernel (TMM) memory resource utilization. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
From the CVE record · f5
When an iRule is configured on a virtual server through the declarative API, cleanup during re-instantiation can increase Traffic Management Microkernel (TMM) memory use. The input does not specify whether an attacker can trigger this behavior or any access or user-interaction requirements.
Teams running F5 BIG-IP Next SPK, BIG-IP Next CNF, or BIG-IP Next for Kubernetes should check their deployments; affected versions are not specified.