What is the severity of CVE-2020-5934?

CVE-2020-5934 is identified as a medium-severity vulnerability that can disrupt traffic to TMM under specific conditions.

How do I fix CVE-2020-5934?

To address CVE-2020-5934, upgrade your BIG-IP APM to a non-affected version beyond the specified 13.1.3.4, 14.1.2.4, or 15.1.1.

What versions of F5 BIG-IP APM are affected by CVE-2020-5934?

F5 BIG-IP APM versions 15.1.0 through 15.1.0.5, 14.1.0 through 14.1.2.3, and 13.1.0 through 13.1.3.3 are affected by CVE-2020-5934.

What impact does CVE-2020-5934 have on the system?

CVE-2020-5934 may cause disruptions in traffic to TMM when simultaneous HTTP requests are made via a TCP Keep-Alive connection.

Is there a workaround for CVE-2020-5934?

While upgrading to a patched version is the recommended solution, limiting concurrent requests to the SLO URL may help mitigate the impact of CVE-2020-5934.

Vulnerability/
CVE-2020-5934

medium

6.5

29/10/2020

4/8/2024

CVE-2020-5934

First published: Thu Oct 29 2020(Updated: )

On BIG-IP APM 15.1.0-15.1.0.5, 14.1.0-14.1.2.3, and 13.1.0-13.1.3.3, when multiple HTTP requests from the same client to configured SAML Single Logout (SLO) URL are passing through a TCP Keep-Alive connection, traffic to TMM can be disrupted.

Credit: f5sirt@f5.com

Affected Software	Affected Version	How to fix
F5 Access Policy Manager	>=13.1.0<13.1.3.4
F5 Access Policy Manager	>=14.1.0<14.1.2.4
F5 Access Policy Manager	>=15.1.0<15.1.1

Never miss a vulnerability like this again

Reference Links

https://support.f5.com/csp/article/K44808538

Frequently Asked Questions

What is the severity of CVE-2020-5934?
CVE-2020-5934 is identified as a medium-severity vulnerability that can disrupt traffic to TMM under specific conditions.
How do I fix CVE-2020-5934?
To address CVE-2020-5934, upgrade your BIG-IP APM to a non-affected version beyond the specified 13.1.3.4, 14.1.2.4, or 15.1.1.
What versions of F5 BIG-IP APM are affected by CVE-2020-5934?
F5 BIG-IP APM versions 15.1.0 through 15.1.0.5, 14.1.0 through 14.1.2.3, and 13.1.0 through 13.1.3.3 are affected by CVE-2020-5934.
What impact does CVE-2020-5934 have on the system?
CVE-2020-5934 may cause disruptions in traffic to TMM when simultaneous HTTP requests are made via a TCP Keep-Alive connection.
Is there a workaround for CVE-2020-5934?
While upgrading to a patched version is the recommended solution, limiting concurrent requests to the SLO URL may help mitigate the impact of CVE-2020-5934.

agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/references
agent/last-modified-date
agent/author
agent/first-publish-date
agent/description
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/f5
canonical/f5 access policy manager
version/f5 access policy manager/13.1.0
version/f5 access policy manager/14.1.0
version/f5 access policy manager/15.1.0

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.

Frequently Asked Questions

What is the severity of CVE-2020-5934?
CVE-2020-5934 is identified as a medium-severity vulnerability that can disrupt traffic to TMM under specific conditions.
How do I fix CVE-2020-5934?
To address CVE-2020-5934, upgrade your BIG-IP APM to a non-affected version beyond the specified 13.1.3.4, 14.1.2.4, or 15.1.1.
What versions of F5 BIG-IP APM are affected by CVE-2020-5934?
F5 BIG-IP APM versions 15.1.0 through 15.1.0.5, 14.1.0 through 14.1.2.3, and 13.1.0 through 13.1.3.3 are affected by CVE-2020-5934.
What impact does CVE-2020-5934 have on the system?
CVE-2020-5934 may cause disruptions in traffic to TMM when simultaneous HTTP requests are made via a TCP Keep-Alive connection.
Is there a workaround for CVE-2020-5934?
While upgrading to a patched version is the recommended solution, limiting concurrent requests to the SLO URL may help mitigate the impact of CVE-2020-5934.