BIG-IP Next (CNF, SPK, and Kubernetes) 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 |
On BIG-IP Next CNF, BIG-IP Next SPK, and BIG-IP Next for Kubernetes systems, repeated undisclosed API calls can cause the Traffic Management Microkernel (TMM) to terminate. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
From the CVE record · f5
BIG-IP Next CNF, SPK, and for Kubernetes are vulnerable to repeated undisclosed API calls that can terminate the Traffic Management Microkernel (TMM). The input does not specify whether authentication, network access, or user interaction is required.
Teams running F5 BIG-IP Next CNF, BIG-IP Next SPK, or BIG-IP Next for Kubernetes should check their deployments; affected versions are not specified, and versions past End of Technical Support were not evaluated.