BIG-IP HTTP/2 vulnerability
F5 BIG-IP · F5 BIG-IP Next for Kubernetes · F5 BIG-IP Next SPK · F5 BIG-IP Next CNF
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| F5 BIG-IP |
| No fix yet |
| F5 BIG-IP Next for Kubernetes |
| No fix yet |
| F5 BIG-IP Next SPK |
F5 BIG-IP · F5 BIG-IP Next for Kubernetes · F5 BIG-IP Next SPK · F5 BIG-IP Next CNF
| Product | Affected | Fixed in |
|---|---|---|
| F5 BIG-IP |
| No fix yet |
| F5 BIG-IP Next for Kubernetes |
| No fix yet |
| F5 BIG-IP Next SPK |
|
| No fix yet |
| F5 BIG-IP Next CNF |
| No fix yet |
When an HTTP/2 profile is configured on a virtual server, undisclosed requests can cause an increase in memory resource utilization.
Impact: System performance can degrade until the TMM process is either forced to restart or is manually restarted. This vulnerability allows a remote, unauthenticated attacker to cause a degradation of service that can lead to a denial-of-service (DoS) on the BIG-IP system. There is no control plane exposure; this is a data plane issue only.
Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
From the CVE record · f5
A virtual server with an HTTP/2 profile can experience increased memory use from undisclosed requests. A remote, unauthenticated attacker can degrade performance and potentially cause a denial of service, including a TMM process restart. This affects the data plane, not the control plane.
Operators of F5 BIG-IP, BIG-IP Next for Kubernetes, BIG-IP Next SPK, and BIG-IP Next CNF should check their deployments; affected versions were not provided.