First published: Thu Feb 06 2020(Updated: )
On BIG-IP 15.0.0-15.0.1.1, 14.1.0-14.1.2.2, 14.0.0-14.0.1, 13.1.0-13.1.3.1, 12.1.0-12.1.5, and 11.6.0-11.6.5.1, the tmm crashes under certain circumstances when using the connector profile if a specific sequence of connections are made.
Credit: f5sirt@f5.com
Affected Software | Affected Version | How to fix |
---|---|---|
F5 Access Policy Manager | >=11.5.2<=11.6.5 | |
F5 Access Policy Manager | >=12.1.0<12.1.5.1 | |
F5 Access Policy Manager | >=13.1.0<13.1.3.2 | |
F5 Access Policy Manager | >=14.0.0<14.0.1.1 | |
F5 Access Policy Manager | >=14.1.0<14.1.2.1 | |
F5 Access Policy Manager | >=15.0.0<15.1.0 | |
F5 BIG-IP Advanced Firewall Manager | >=11.5.2<=11.6.5 | |
F5 BIG-IP Advanced Firewall Manager | >=12.1.0<12.1.5.1 | |
F5 BIG-IP Advanced Firewall Manager | >=13.1.0<13.1.3.2 | |
F5 BIG-IP Advanced Firewall Manager | >=14.0.0<14.0.1.1 | |
F5 BIG-IP Advanced Firewall Manager | >=14.1.0<14.1.2.1 | |
F5 BIG-IP Advanced Firewall Manager | >=15.0.0<15.1.0 | |
F5 BIG-IP Analytics | >=11.5.2<=11.6.5 | |
F5 BIG-IP Analytics | >=12.1.0<12.1.5.1 | |
F5 BIG-IP Analytics | >=13.1.0<13.1.3.2 | |
F5 BIG-IP Analytics | >=14.0.0<14.0.1.1 | |
F5 BIG-IP Analytics | >=14.1.0<14.1.2.1 | |
F5 BIG-IP Analytics | >=15.0.0<15.1.0 | |
f5 big-ip application acceleration manager | >=11.5.2<=11.6.5 | |
f5 big-ip application acceleration manager | >=12.1.0<12.1.5.1 | |
f5 big-ip application acceleration manager | >=13.1.0<13.1.3.2 | |
f5 big-ip application acceleration manager | >=14.0.0<14.0.1.1 | |
f5 big-ip application acceleration manager | >=14.1.0<14.1.2.1 | |
f5 big-ip application acceleration manager | >=15.0.0<15.1.0 | |
F5 Application Security Manager | >=11.5.2<=11.6.5 | |
F5 Application Security Manager | >=12.1.0<12.1.5.1 | |
F5 Application Security Manager | >=13.1.0<13.1.3.2 | |
F5 Application Security Manager | >=14.0.0<14.0.1.1 | |
F5 Application Security Manager | >=14.1.0<14.1.2.1 | |
F5 Application Security Manager | >=15.0.0<15.1.0 | |
f5 big-ip domain name system | >=11.5.2<=11.6.5 | |
f5 big-ip domain name system | >=12.1.0<12.1.5.1 | |
f5 big-ip domain name system | >=13.1.0<13.1.3.2 | |
f5 big-ip domain name system | >=14.0.0<14.0.1.1 | |
f5 big-ip domain name system | >=14.1.0<14.1.2.1 | |
f5 big-ip domain name system | >=15.0.0<15.1.0 | |
F5 BIG-IP Edge Gateway | >=11.5.2<=11.6.5 | |
F5 BIG-IP Edge Gateway | >=12.1.0<12.1.5.1 | |
F5 BIG-IP Edge Gateway | >=13.1.0<13.1.3.2 | |
F5 BIG-IP Edge Gateway | >=14.0.0<14.0.1.1 | |
F5 BIG-IP Edge Gateway | >=14.1.0<14.1.2.1 | |
F5 BIG-IP Edge Gateway | >=15.0.0<15.1.0 | |
F5 BIG-IP fraud protection services | >=11.5.2<=11.6.5 | |
F5 BIG-IP fraud protection services | >=12.1.0<12.1.5.1 | |
F5 BIG-IP fraud protection services | >=13.1.0<13.1.3.2 | |
F5 BIG-IP fraud protection services | >=14.0.0<14.0.1.1 | |
F5 BIG-IP fraud protection services | >=14.1.0<14.1.2.1 | |
F5 BIG-IP fraud protection services | >=15.0.0<15.1.0 | |
F5 BIG-IP Global Traffic Manager | >=11.5.2<=11.6.5 | |
F5 BIG-IP Global Traffic Manager | >=12.1.0<12.1.5.1 | |
F5 BIG-IP Global Traffic Manager | >=13.1.0<13.1.3.2 | |
F5 BIG-IP Global Traffic Manager | >=14.0.0<14.0.1.1 | |
F5 BIG-IP Global Traffic Manager | >=14.1.0<14.1.2.1 | |
F5 BIG-IP Global Traffic Manager | >=15.0.0<15.1.0 | |
F5 BIG-IP | >=11.5.2<=11.6.5 | |
F5 BIG-IP | >=12.1.0<12.1.5.1 | |
F5 BIG-IP | >=13.1.0<13.1.3.2 | |
F5 BIG-IP | >=14.0.0<14.0.1.1 | |
F5 BIG-IP | >=14.1.0<14.1.2.1 | |
F5 BIG-IP | >=15.0.0<15.1.0 | |
F5 BIG-IP Local Traffic Manager | >=11.5.2<=11.6.5 | |
F5 BIG-IP Local Traffic Manager | >=12.1.0<12.1.5.1 | |
F5 BIG-IP Local Traffic Manager | >=13.1.0<13.1.3.2 | |
F5 BIG-IP Local Traffic Manager | >=14.0.0<14.0.1.1 | |
F5 BIG-IP Local Traffic Manager | >=14.1.0<14.1.2.1 | |
F5 BIG-IP Local Traffic Manager | >=15.0.0<15.1.0 | |
F5 BIG-IP Policy Enforcement Manager | >=11.5.2<=11.6.5 | |
F5 BIG-IP Policy Enforcement Manager | >=12.1.0<12.1.5.1 | |
F5 BIG-IP Policy Enforcement Manager | >=13.1.0<13.1.3.2 | |
F5 BIG-IP Policy Enforcement Manager | >=14.0.0<14.0.1.1 | |
F5 BIG-IP Policy Enforcement Manager | >=14.1.0<14.1.2.1 | |
F5 BIG-IP Policy Enforcement Manager | >=15.0.0<15.1.0 | |
F5 BIG-IP WebAccelerator | >=11.5.2<=11.6.5 | |
F5 BIG-IP WebAccelerator | >=12.1.0<12.1.5.1 | |
F5 BIG-IP WebAccelerator | >=13.1.0<13.1.3.2 | |
F5 BIG-IP WebAccelerator | >=14.0.0<14.0.1.1 | |
F5 BIG-IP WebAccelerator | >=14.1.0<14.1.2.1 | |
F5 BIG-IP WebAccelerator | >=15.0.0<15.1.0 | |
F5 BIG-IP and BIG-IQ Centralized Management | >=5.1.0<=5.4.0 | |
F5 BIG-IP and BIG-IQ Centralized Management | >=6.0.0<=6.1.0 | |
F5 BIG-IP and BIG-IQ Centralized Management | =7.0.0 | |
F5 Enterprise Manager | =3.1.1 | |
F5 iWorkflow | =2.3.0 | |
F5 Traffix Systems Signaling Delivery Controller | >=5.0.0<=5.1.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-5854 has been classified as a critical vulnerability due to the risk of system crashes affecting service availability.
To mitigate CVE-2020-5854, upgrade your F5 BIG-IP systems to the latest supported version as specified in the vendor advisory.
CVE-2020-5854 affects F5 BIG-IP versions 11.6.0 to 11.6.5, 12.1.0 to 12.1.5, and several others up to 15.0.1.1.
CVE-2020-5854 can cause the Traffic Management Microkernel (TMM) to crash, potentially leading to denial of service.
While an immediate workaround is not specified, implementing strict control over connection sequences may help reduce risk until a patch is applied.