CVE-2020-5876: Race Condition

Published 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.

Affected Software

55 affected components
F5 BIG-IP Access Policy Manager>=11.6.1<=11.6.5.1
F5 BIG-IP Access Policy Manager>=12.1.0<=12.1.5.1
F5 BIG-IP Access Policy Manager>=13.1.0<=13.1.3.3
F5 BIG-IP Access Policy Manager>=14.1.0<=14.1.2.3
F5 BIG-IP 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 BIG-IP Application Security Manager>=11.6.1<=11.6.5.1
F5 BIG-IP Application Security Manager>=12.1.0<=12.1.5.1
F5 BIG-IP Application Security Manager>=13.1.0<=13.1.3.3
F5 BIG-IP Application Security Manager>=14.1.0<=14.1.2.3
F5 BIG-IP Application Security Manager>=15.0.0<=15.1.0.3
F5 Big-ip Domain Name System>=11.6.1<=11.6.5.1
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.3
F5 Big-ip Domain Name System>=14.1.0<=14.1.2.3
F5 Big-ip Domain Name System>=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
F5 Big-ip Global Traffic Manager>=11.6.1<=11.6.5.1
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.3
F5 Big-ip Global Traffic Manager>=14.1.0<=14.1.2.3
F5 Big-ip Global 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
F5 Big-ip Local Traffic Manager>=11.6.1<=11.6.5.1
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.3
F5 Big-ip Local Traffic Manager>=14.1.0<=14.1.2.3
F5 Big-ip Local 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

Event History

Apr 30, 2020
CVE Published
via MITRE·08:30 PM
Data Sourced
via MITRE·08:30 PM
DescriptionWeakness

Frequently Asked Questions

1

What is the severity of CVE-2020-5876?

The severity of CVE-2020-5876 is classified as high due to potential unauthorized access through unencrypted connections.

2

How do I fix CVE-2020-5876?

To fix CVE-2020-5876, upgrade to the latest versions of affected F5 BIG-IP products that address the vulnerability.

3

Which versions of F5 BIG-IP are affected by CVE-2020-5876?

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.

4

What processes are involved in the CVE-2020-5876 vulnerability?

The CVE-2020-5876 vulnerability involves a race condition between the mcpd process and other processes during configuration synchronization.

5

Can CVE-2020-5876 lead to data exposure?

Yes, CVE-2020-5876 may lead to data exposure due to the possibility of unencrypted connections to sync peers.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203