First published: Thu Apr 30 2020(Updated: )
On BIG-IP 15.0.0-15.0.1.3, 14.1.0-14.1.2.3, 13.1.0-13.1.3.3, 12.1.0-12.1.5.1, and 11.6.1-11.6.5.1, a race condition exists where mcpd and other processes may make unencrypted connection attempts to a new configuration sync peer. The race condition can occur when changing the ConfigSync IP address of a peer, adding a new peer, or when the Traffic Management Microkernel (TMM) first starts up.
Credit: f5sirt@f5.com
Affected Software | Affected Version | How to fix |
---|---|---|
F5 Access Policy Manager | >=11.6.1<=11.6.5.1 | |
F5 Access Policy Manager | >=12.1.0<=12.1.5.1 | |
F5 Access Policy Manager | >=13.1.0<=13.1.3.3 | |
F5 Access Policy Manager | >=14.1.0<=14.1.2.3 | |
F5 Access Policy Manager | >=15.0.0<=15.1.0.3 | |
F5 BIG-IP Advanced Firewall Manager | >=11.6.1<=11.6.5.1 | |
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.3 | |
F5 BIG-IP Advanced Firewall Manager | >=14.1.0<=14.1.2.3 | |
F5 BIG-IP Advanced Firewall Manager | >=15.0.0<=15.1.0.3 | |
F5 BIG-IP Analytics | >=11.6.1<=11.6.5.1 | |
F5 BIG-IP Analytics | >=12.1.0<=12.1.5.1 | |
F5 BIG-IP Analytics | >=13.1.0<=13.1.3.3 | |
F5 BIG-IP Analytics | >=14.1.0<=14.1.2.3 | |
F5 BIG-IP Analytics | >=15.0.0<=15.1.0.3 | |
F5 BIG-IP Application Acceleration Manager | >=11.6.1<=11.6.5.1 | |
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.3 | |
F5 BIG-IP Application Acceleration Manager | >=14.1.0<=14.1.2.3 | |
F5 BIG-IP Application Acceleration Manager | >=15.0.0<=15.1.0.3 | |
F5 Application Security Manager | >=11.6.1<=11.6.5.1 | |
F5 Application Security Manager | >=12.1.0<=12.1.5.1 | |
F5 Application Security Manager | >=13.1.0<=13.1.3.3 | |
F5 Application Security Manager | >=14.1.0<=14.1.2.3 | |
F5 Application Security Manager | >=15.0.0<=15.1.0.3 | |
F5 BIG-IP | >=11.6.1<=11.6.5.1 | |
F5 BIG-IP | >=12.1.0<=12.1.5.1 | |
F5 BIG-IP | >=13.1.0<=13.1.3.3 | |
F5 BIG-IP | >=14.1.0<=14.1.2.3 | |
F5 BIG-IP | >=15.0.0<=15.1.0.3 | |
F5 BIG-IP Fraud Protection Service | >=11.6.1<=11.6.5.1 | |
F5 BIG-IP Fraud Protection Service | >=12.1.0<=12.1.5.1 | |
F5 BIG-IP Fraud Protection Service | >=13.1.0<=13.1.3.3 | |
F5 BIG-IP Fraud Protection Service | >=14.1.0<=14.1.2.3 | |
F5 BIG-IP Fraud Protection Service | >=15.0.0<=15.1.0.3 | |
Riverbed SteelApp Traffic Manager | >=11.6.1<=11.6.5.1 | |
Riverbed SteelApp Traffic Manager | >=12.1.0<=12.1.5.1 | |
Riverbed SteelApp Traffic Manager | >=13.1.0<=13.1.3.3 | |
Riverbed SteelApp Traffic Manager | >=14.1.0<=14.1.2.3 | |
Riverbed SteelApp Traffic Manager | >=15.0.0<=15.1.0.3 | |
F5 BIG-IP Link Controller | >=11.6.1<=11.6.5.1 | |
F5 BIG-IP Link Controller | >=12.1.0<=12.1.5.1 | |
F5 BIG-IP Link Controller | >=13.1.0<=13.1.3.3 | |
F5 BIG-IP Link Controller | >=14.1.0<=14.1.2.3 | |
F5 BIG-IP Link Controller | >=15.0.0<=15.1.0.3 | |
Riverbed SteelApp Traffic Manager | >=11.6.1<=11.6.5.1 | |
Riverbed SteelApp Traffic Manager | >=12.1.0<=12.1.5.1 | |
Riverbed SteelApp Traffic Manager | >=13.1.0<=13.1.3.3 | |
Riverbed SteelApp Traffic Manager | >=14.1.0<=14.1.2.3 | |
Riverbed SteelApp Traffic Manager | >=15.0.0<=15.1.0.3 | |
F5 BIG-IP Policy Enforcement Manager | >=11.6.1<=11.6.5.1 | |
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.3 | |
F5 BIG-IP Policy Enforcement Manager | >=14.1.0<=14.1.2.3 | |
F5 BIG-IP Policy Enforcement Manager | >=15.0.0<=15.1.0.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2020-5876 is classified as high due to potential unauthorized access through unencrypted connections.
To fix CVE-2020-5876, upgrade to the latest versions of affected F5 BIG-IP products that address the vulnerability.
CVE-2020-5876 affects F5 BIG-IP versions 11.6.1 to 11.6.5.1, 12.1.0 to 12.1.5.1, 13.1.0 to 13.1.3.3, 14.1.0 to 14.1.2.3, and 15.0.0 to 15.0.1.3.
The CVE-2020-5876 vulnerability involves a race condition between the mcpd process and other processes during configuration synchronization.
Yes, CVE-2020-5876 may lead to data exposure due to the possibility of unencrypted connections to sync peers.