BIG-IP: When an HTTP/2 profile is configured on a virtual server, undisclosed requests
Summary
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. Affected products named by the advisory: BIG-IP Next for Kubernetes; BIG-IP Next SPK; BIG-IP Next CNF.
What this means
In plain English
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. The official description indicates that exploitation does not require prior authentication.
Vulnerable items
- BIG-IP — F5 BIG-IP provides application delivery, load balancing and network security services.
- BIG-IP Next for Kubernetes — F5 BIG-IP provides application delivery, load balancing and network security services.
- BIG-IP Next SPK — F5 BIG-IP provides application delivery, load balancing and network security services.
- BIG-IP Next CNF — F5 BIG-IP provides application delivery, load balancing and network security services.
Recommended action
Primary action: update to a vendor-listed fixed release: 21.1.0.1, 21.0.0.3, 17.5.1.8, 17.1.3.4, 2.3.2, 2.2.3, 1.7.18, 1.4.3.
Rewritten locally from the scraped official advisory data above; no generative API is used. The vendor advisory is authoritative.
- BIG-IP 21.1.0 before 21.1.0.1
- BIG-IP 21.0.0 before 21.0.0.3
- BIG-IP 17.5.0 before 17.5.1.8
- BIG-IP 17.1.0 before 17.1.3.4
- BIG-IP Next for Kubernetes 2.3.0 before 2.3.2
- BIG-IP Next for Kubernetes 2.0.0 before 2.2.3
- BIG-IP Next SPK 1.9.0
- BIG-IP Next SPK 1.7.0 before 1.7.18
- BIG-IP Next CNF 2.3.0 before 2.3.2
- BIG-IP Next CNF 2.0.0 before 2.2.3
- BIG-IP Next CNF 1.1.0 before 1.4.3
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
- 21.1.0.1
- 21.0.0.3
- 17.5.1.8
- 17.1.3.4
- 2.3.2
- 2.2.3
- 1.7.18
- 1.4.3
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
Mitigation
Upgrade to a fixed release: 21.1.0.1, 21.0.0.3, 17.5.1.8, 17.1.3.4, 2.3.2, 2.2.3. That is the remediation for this advisory.
The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.