BIG-IP SSL/TLS vulnerability
F5 BIG-IP · 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 |
|
|
| F5 BIG-IP Next SPK |
| No fix yet |
F5 BIG-IP · F5 BIG-IP Next SPK · F5 BIG-IP Next CNF · F5 BIG-IP Next for Kubernetes
| Product | Affected | Fixed in |
|---|---|---|
| F5 BIG-IP |
|
|
| F5 BIG-IP Next SPK |
| No fix yet |
| F5 BIG-IP Next CNF |
| No fix yet |
| F5 BIG-IP Next for Kubernetes |
| No fix yet |
When an SSL profile is configured on a virtual server on BIG-IP Virtual Edition (VE) without Intel QuickAssist Technology (QAT) or on BIG-IP hardware platforms with the database variable crypto.hwacceleration set to disabled, undisclosed traffic 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
On BIG-IP Virtual Edition without Intel QuickAssist Technology, or on BIG-IP hardware with crypto.hwacceleration disabled, a virtual server configured with an SSL profile is vulnerable. Undisclosed traffic to that virtual server can cause the Traffic Management Microkernel (TMM) to terminate. The input does not specify whether authentication or user interaction is required.
Teams running BIG-IP Virtual Edition or BIG-IP hardware under these conditions should check their deployments; affected versions are not specified.