BIG-IP HTTP/2 vulnerability
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 21.1.0.1, 21.0.0.3, 17.5.1.8, 17.1.3.4, 2.3.2, and 3 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- F5 BIG-IP
From 21.1.0 · fixed in 21.1.0.1; From 21.0.0 · fixed in 21.0.0.3; From 17.5.0 · fixed in 17.5.1.8; From 17.1.0 · fixed in 17.1.3.4
- F5 BIG-IP Next for Kubernetes
From 2.3.0 · fixed in 2.3.2; From 2.0.0 · fixed in 2.2.3
- F5 BIG-IP Next SPK
From 1.9.0; From 1.7.0 · fixed in 1.7.18
- F5 BIG-IP Next CNF
From 2.3.0 · fixed in 2.3.2; From 2.0.0 · fixed in 2.2.3; From 1.1.0 · fixed in 1.4.3