What is the severity of CVE-2018-5505?

CVE-2018-5505 is classified as a critical vulnerability due to potential service disruption.

How do I fix CVE-2018-5505?

To fix CVE-2018-5505, you should upgrade to a version of F5 BIG-IP greater than 13.1.0.3.

What software is affected by CVE-2018-5505?

CVE-2018-5505 affects F5 BIG-IP Analytics and F5 Application Security Manager versions 13.1.0 to 13.1.0.3.

What could happen if CVE-2018-5505 is exploited?

If exploited, CVE-2018-5505 may cause the TMM process to restart, leading to potential downtime.

Is there any workaround for CVE-2018-5505?

Currently, there are no official workarounds for CVE-2018-5505 other than updating to the latest software version.

Vulnerability/
CVE-2018-5505

medium

5.9

22/3/2018

16/9/2024

CVE-2018-5505

First published: Thu Mar 22 2018(Updated: )

On F5 BIG-IP versions 13.1.0 - 13.1.0.3, when ASM and AVR are both provisioned, TMM may restart while processing DNS requests when the virtual server is configured with a DNS profile and the Protocol setting is set to TCP.

Credit: f5sirt@f5.com

Affected Software	Affected Version	How to fix
F5 BIG-IP Analytics	>=13.1.0<13.1.0.4
F5 Application Security Manager	>=13.1.0<13.1.0.4

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-5505?
CVE-2018-5505 is classified as a critical vulnerability due to potential service disruption.
How do I fix CVE-2018-5505?
To fix CVE-2018-5505, you should upgrade to a version of F5 BIG-IP greater than 13.1.0.3.
What software is affected by CVE-2018-5505?
CVE-2018-5505 affects F5 BIG-IP Analytics and F5 Application Security Manager versions 13.1.0 to 13.1.0.3.
What could happen if CVE-2018-5505 is exploited?
If exploited, CVE-2018-5505 may cause the TMM process to restart, leading to potential downtime.
Is there any workaround for CVE-2018-5505?
Currently, there are no official workarounds for CVE-2018-5505 other than updating to the latest software version.

agent/type
agent/softwarecombine
agent/references
agent/author
agent/severity
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/f5
canonical/f5 big-ip analytics
version/f5 big-ip analytics/13.1.0
canonical/f5 application security manager
version/f5 application security manager/13.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-2018-5505?
CVE-2018-5505 is classified as a critical vulnerability due to potential service disruption.
How do I fix CVE-2018-5505?
To fix CVE-2018-5505, you should upgrade to a version of F5 BIG-IP greater than 13.1.0.3.
What software is affected by CVE-2018-5505?
CVE-2018-5505 affects F5 BIG-IP Analytics and F5 Application Security Manager versions 13.1.0 to 13.1.0.3.
What could happen if CVE-2018-5505 is exploited?
If exploited, CVE-2018-5505 may cause the TMM process to restart, leading to potential downtime.
Is there any workaround for CVE-2018-5505?
Currently, there are no official workarounds for CVE-2018-5505 other than updating to the latest software version.