high
7.5
Advisory Published
Updated

CVE-2020-5931

First published: Thu Oct 29 2020(Updated: )

On BIG-IP 15.1.0-15.1.0.5, 14.1.0-14.1.2.3, 13.1.0-13.1.3.4, 12.1.0-12.1.5.2, and 11.6.1-11.6.5.2, Virtual servers with a OneConnect profile may incorrectly handle WebSockets related HTTP response headers, causing TMM to restart.

Credit: f5sirt@f5.com

Affected SoftwareAffected VersionHow to fix
F5 BIG-IP Access Policy Manager>=11.6.1<=11.6.5.2
F5 BIG-IP Access Policy Manager>=12.1.0<=12.1.5.2
F5 BIG-IP Access Policy Manager>=13.1.0<=13.1.3.4
F5 BIG-IP Access Policy Manager>=14.0.0<14.1.2.5
F5 BIG-IP Access Policy Manager>=15.0.0<15.1.1
F5 BIG-IP Advanced Firewall Manager>=11.6.1<=11.6.5.2
F5 BIG-IP Advanced Firewall Manager>=12.1.0<=12.1.5.2
F5 BIG-IP Advanced Firewall Manager>=13.1.0<=13.1.3.4
F5 BIG-IP Advanced Firewall Manager>=14.0.0<14.1.2.5
F5 BIG-IP Advanced Firewall Manager>=15.0.0<15.1.1
F5 BIG-IP Analytics>=11.6.1<=11.6.5.2
F5 BIG-IP Analytics>=12.1.0<=12.1.5.2
F5 BIG-IP Analytics>=13.1.0<=13.1.3.4
F5 BIG-IP Analytics>=14.0.0<14.1.2.5
F5 BIG-IP Analytics>=15.0.0<15.1.1
f5 big-ip application acceleration manager>=11.6.1<=11.6.5.2
f5 big-ip application acceleration manager>=12.1.0<=12.1.5.2
f5 big-ip application acceleration manager>=13.1.0<=13.1.3.4
f5 big-ip application acceleration manager>=14.0.0<14.1.2.5
f5 big-ip application acceleration manager>=15.0.0<15.1.1
F5 BIG-IP Application Security Manager>=11.6.1<=11.6.5.2
F5 BIG-IP Application Security Manager>=12.1.0<=12.1.5.2
F5 BIG-IP Application Security Manager>=13.1.0<=13.1.3.4
F5 BIG-IP Application Security Manager>=14.0.0<14.1.2.5
F5 BIG-IP Application Security Manager>=15.0.0<15.1.1
f5 big-ip domain name system>=11.6.1<=11.6.5.2
f5 big-ip domain name system>=12.1.0<=12.1.5.2
f5 big-ip domain name system>=13.1.0<=13.1.3.4
f5 big-ip domain name system>=14.0.0<14.1.2.5
f5 big-ip domain name system>=15.0.0<15.1.1
f5 big-ip fraud protection service>=11.6.1<=11.6.5.2
f5 big-ip fraud protection service>=12.1.0<=12.1.5.2
f5 big-ip fraud protection service>=13.1.0<=13.1.3.4
f5 big-ip fraud protection service>=14.0.0<14.1.2.5
f5 big-ip fraud protection service>=15.0.0<15.1.1
F5 BIG-IP Global Traffic Manager>=11.6.1<=11.6.5.2
F5 BIG-IP Global Traffic Manager>=12.1.0<=12.1.5.2
F5 BIG-IP Global Traffic Manager>=13.1.0<=13.1.3.4
F5 BIG-IP Global Traffic Manager>=14.0.0<14.1.2.5
F5 BIG-IP Global Traffic Manager>=15.0.0<15.1.1
f5 big-ip link controller>=11.6.1<=11.6.5.2
f5 big-ip link controller>=12.1.0<=12.1.5.2
f5 big-ip link controller>=13.1.0<=13.1.3.4
f5 big-ip link controller>=14.0.0<14.1.2.5
f5 big-ip link controller>=15.0.0<15.1.1
F5 BIG-IP Local Traffic Manager>=11.5.2<=11.6.5.2
F5 BIG-IP Local Traffic Manager>=12.1.0<=12.1.5.2
F5 BIG-IP Local Traffic Manager>=13.1.0<=13.1.3.4
F5 BIG-IP Local Traffic Manager>=14.0.0<14.1.2.5
F5 BIG-IP Local Traffic Manager>=15.0.0<15.1.1
F5 BIG-IP Policy Enforcement Manager>=11.6.1<=11.6.5.2
F5 BIG-IP Policy Enforcement Manager>=12.1.0<=12.1.5.2
F5 BIG-IP Policy Enforcement Manager>=13.1.0<=13.1.3.4
F5 BIG-IP Policy Enforcement Manager>=14.0.0<14.1.2.5
F5 BIG-IP Policy Enforcement Manager>=15.0.0<15.1.1

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2020-5931?

    CVE-2020-5931 has been rated as high severity due to potential disruption of service through incorrect handling of WebSockets headers.

  • How do I fix CVE-2020-5931?

    To remediate CVE-2020-5931, upgrade your F5 BIG-IP systems to a version later than 15.1.0.5, 14.1.2.3, 13.1.3.4, 12.1.5.2, or 11.6.5.2.

  • Which F5 BIG-IP versions are affected by CVE-2020-5931?

    F5 BIG-IP versions 15.1.0-15.1.0.5, 14.1.0-14.1.2.3, 13.1.0-13.1.3.4, 12.1.0-12.1.5.2, and 11.6.1-11.6.5.2 are affected by CVE-2020-5931.

  • What impact does CVE-2020-5931 have on F5 BIG-IP users?

    CVE-2020-5931 can lead to TMM (Traffic Management Microkernel) restarts, which may cause temporary service interruptions.

  • Is there a workaround for CVE-2020-5931?

    While the recommended action is to update to a secure version, users may also consider disabling the OneConnect profile on affected virtual servers as a temporary workaround.

Company

Resources

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203