HTTP/2 Vulnerability
F5 BIG-IP · F5 BIG-IP Next · 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 |
| No fix yet |
| F5 BIG-IP Next SPK |
|
F5 BIG-IP · F5 BIG-IP Next · F5 BIG-IP Next SPK · F5 BIG-IP Next CNF
| Product | Affected | Fixed in |
|---|---|---|
| F5 BIG-IP |
| No fix yet |
| F5 BIG-IP Next |
| No fix yet |
| F5 BIG-IP Next SPK |
|
≥ 1.7.0 · < *| No fix yet |
| F5 BIG-IP Next CNF |
| No fix yet |
| F5 BIG-IP Next for Kubernetes |
| No fix yet |
An HTTP/2 implementation flaw allows a denial-of-service (DoS) that uses malformed HTTP/2 control frames in order to break the max concurrent streams limit (HTTP/2 MadeYouReset Attack).
Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
From the CVE record · f5
An HTTP/2 implementation flaw affects F5 BIG-IP and BIG-IP Next products. An attacker can send malformed HTTP/2 control frames to bypass the maximum concurrent streams limit and cause a denial of service. The input does not specify whether authentication or user interaction is required.
Operators of F5 BIG-IP, BIG-IP Next, BIG-IP Next SPK, BIG-IP Next CNF, and BIG-IP Next for Kubernetes should check their deployments; affected versions are not specified.