BIG-IP PEM vulnerability
F5 BIG-IP · F5 BIG-IP Next CNF · F5 BIG-IP Next for Kubernetes
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| F5 BIG-IP |
| No fix yet |
| F5 BIG-IP Next CNF |
| No fix yet |
| F5 BIG-IP Next for Kubernetes |
F5 BIG-IP · F5 BIG-IP Next CNF · F5 BIG-IP Next for Kubernetes
| Product | Affected | Fixed in |
|---|---|---|
| F5 BIG-IP |
| No fix yet |
| F5 BIG-IP Next CNF |
| No fix yet |
| F5 BIG-IP Next for Kubernetes |
|
| No fix yet |
When a classification profile is configured on a virtual server without an HTTP or HTTP/2 profile, undisclosed requests 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
A virtual server is vulnerable when it has a classification profile but no HTTP or HTTP/2 profile. Undisclosed requests can cause the Traffic Management Microkernel (TMM) to terminate. The input does not specify authentication or user-interaction requirements.
Operators of F5 BIG-IP, F5 BIG-IP Next CNF, and F5 BIG-IP Next for Kubernetes should check their deployments; affected versions are not specified.