First published: Fri Feb 12 2021(Updated: )
On BIG-IP version 16.0.x before 16.0.1.1, 15.1.x before 15.1.2.1, and 14.1.x before 14.1.3.1, under some circumstances, Traffic Management Microkernel (TMM) may restart on the BIG-IP system while passing large bursts of traffic. Note: Software versions which have reached End of Software Development (EoSD) are not evaluated.
Credit: f5sirt@f5.com
Affected Software | Affected Version | How to fix |
---|---|---|
F5 BIG-IP Access Policy Manager | >=14.1.0<14.1.3.1 | |
F5 BIG-IP Access Policy Manager | >=15.1.0<15.1.2.1 | |
F5 BIG-IP Access Policy Manager | >=16.0.0<16.0.1.1 | |
F5 BIG-IP Advanced Firewall Manager | >=14.1.0<14.1.3.1 | |
F5 BIG-IP Advanced Firewall Manager | >=15.1.0<15.1.2.1 | |
F5 BIG-IP Advanced Firewall Manager | >=16.0.0<16.0.1.1 | |
F5 BIG-IP Advanced Web Application Firewall | >=14.1.0<14.1.3.1 | |
F5 BIG-IP Advanced Web Application Firewall | >=15.1.0<15.1.2.1 | |
F5 BIG-IP Advanced Web Application Firewall | >=16.0.0<16.0.1.1 | |
F5 BIG-IP Analytics | >=14.1.0<14.1.3.1 | |
F5 BIG-IP Analytics | >=15.1.0<15.1.2.1 | |
F5 BIG-IP Analytics | >=16.0.0<16.0.1.1 | |
f5 big-ip application acceleration manager | >=14.1.0<14.1.3.1 | |
f5 big-ip application acceleration manager | >=15.1.0<15.1.2.1 | |
f5 big-ip application acceleration manager | >=16.0.0<16.0.1.1 | |
F5 BIG-IP Application Security Manager | >=14.1.0<14.1.3.1 | |
F5 BIG-IP Application Security Manager | >=15.1.0<15.1.2.1 | |
F5 BIG-IP Application Security Manager | >=16.0.0<16.0.1.1 | |
F5 BIG-IP DDoS Hybrid Defender | >=14.1.0<14.1.3.1 | |
F5 BIG-IP DDoS Hybrid Defender | >=15.1.0<15.1.2.1 | |
F5 BIG-IP DDoS Hybrid Defender | >=16.0.0<16.0.1.1 | |
f5 big-ip domain name system | >=14.1.0<14.1.3.1 | |
f5 big-ip domain name system | >=15.1.0<15.1.2.1 | |
f5 big-ip domain name system | >=16.0.0<16.0.1.1 | |
f5 big-ip fraud protection service | >=14.1.0<14.1.3.1 | |
f5 big-ip fraud protection service | >=15.1.0<15.1.2.1 | |
f5 big-ip fraud protection service | >=16.0.0<16.0.1.1 | |
F5 BIG-IP Global Traffic Manager | >=14.1.0<14.1.3.1 | |
F5 BIG-IP Global Traffic Manager | >=15.1.0<15.1.2.1 | |
F5 BIG-IP Global Traffic Manager | >=16.0.0<16.0.1.1 | |
f5 big-ip link controller | >=14.1.0<14.1.3.1 | |
f5 big-ip link controller | >=15.1.0<15.1.2.1 | |
f5 big-ip link controller | >=16.0.0<16.0.1.1 | |
F5 BIG-IP Local Traffic Manager | >=14.1.0<14.1.3.1 | |
F5 BIG-IP Local Traffic Manager | >=15.1.0<15.1.2.1 | |
F5 BIG-IP Local Traffic Manager | >=16.0.0<16.0.1.1 | |
F5 BIG-IP Policy Enforcement Manager | >=14.1.0<14.1.3.1 | |
F5 BIG-IP Policy Enforcement Manager | >=15.1.0<15.1.2.1 | |
F5 BIG-IP Policy Enforcement Manager | >=16.0.0<16.0.1.1 | |
F5 BIG-IP SSL Orchestrator | >=14.1.0<14.1.3.1 | |
F5 BIG-IP SSL Orchestrator | >=15.1.0<15.1.2.1 | |
F5 BIG-IP SSL Orchestrator | >=16.0.0<16.0.1.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2021-22975 is classified as high due to potential system downtime during large bursts of traffic.
To fix CVE-2021-22975, you should upgrade to the latest software versions, which are 16.0.1.1, 15.1.2.1, or 14.1.3.1, or later.
CVE-2021-22975 affects F5 BIG-IP systems running versions prior to 16.0.1.1, 15.1.2.1, and 14.1.3.1.
Symptoms of a vulnerability from CVE-2021-22975 may include sudden Traffic Management Microkernel (TMM) restarts during high traffic loads.
There are no specific workarounds for CVE-2021-22975; upgrading to secure versions is strongly recommended.