BIG-IP HTTP/2 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 HTTP/2 profile and an iRule containing the HTTP::redirect or HTTP::respond command are configured on a virtual server, undisclosed requests can cause the Traffic Management Microkernel (TMM) process to terminate. 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/2 profile and an iRule containing HTTP::redirect or HTTP::respond is vulnerable. Undisclosed requests to that virtual server can cause the Traffic Management Microkernel (TMM) process to terminate; the input does not specify authentication or user-interaction requirements.
Operators of F5 BIG-IP, BIG-IP Next SPK, BIG-IP Next CNF, and BIG-IP Next for Kubernetes should check affected versions in the vendor advisory; the input lists no versions.