What is the severity of CVE-2021-23018?

CVE-2021-23018 has a medium severity rating due to the potential exposure of sensitive data due to cleartext communication.

How do I fix CVE-2021-23018?

To fix CVE-2021-23018, upgrade NGINX Controller to version 3.4.0 or later where TLS is implemented for intra-cluster communication.

What impact does CVE-2021-23018 have on my network?

CVE-2021-23018 may allow unauthorized access to sensitive information as communication within the cluster is not secured.

Which versions are affected by CVE-2021-23018?

CVE-2021-23018 affects F5 NGINX Controller versions from 3.0.0 to prior to 3.4.0.

Is there a workaround for CVE-2021-23018?

There are no recommended workarounds for CVE-2021-23018; the best course of action is to update to an unaffected version.

Vulnerability/
CVE-2021-23018

high

7.4

CWE

319

1/6/2021

11/6/2021

CVE-2021-23018

First published: Tue Jun 01 2021(Updated: )

Intra-cluster communication does not use TLS. The services within the NGINX Controller 3.x before 3.4.0 namespace are using cleartext protocols inside the cluster.

Credit: f5sirt@f5.com

Affected Software	Affected Version	How to fix
F5 Nginx Controller	>=3.0.0<=3.4.0

Never miss a vulnerability like this again

Reference Links

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

Frequently Asked Questions

What is the severity of CVE-2021-23018?
CVE-2021-23018 has a medium severity rating due to the potential exposure of sensitive data due to cleartext communication.
How do I fix CVE-2021-23018?
To fix CVE-2021-23018, upgrade NGINX Controller to version 3.4.0 or later where TLS is implemented for intra-cluster communication.
What impact does CVE-2021-23018 have on my network?
CVE-2021-23018 may allow unauthorized access to sensitive information as communication within the cluster is not secured.
Which versions are affected by CVE-2021-23018?
CVE-2021-23018 affects F5 NGINX Controller versions from 3.0.0 to prior to 3.4.0.
Is there a workaround for CVE-2021-23018?
There are no recommended workarounds for CVE-2021-23018; the best course of action is to update to an unaffected version.

collector/nvd-index
agent/author
agent/weakness
agent/references
agent/severity
agent/description
agent/tags
agent/type
agent/event
agent/last-modified-date
agent/softwarecombine
agent/first-publish-date
vendor/f5
canonical/f5 nginx controller
version/f5 nginx controller/3.0.0
version/f5 nginx controller/3.4.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-2021-23018?
CVE-2021-23018 has a medium severity rating due to the potential exposure of sensitive data due to cleartext communication.
How do I fix CVE-2021-23018?
To fix CVE-2021-23018, upgrade NGINX Controller to version 3.4.0 or later where TLS is implemented for intra-cluster communication.
What impact does CVE-2021-23018 have on my network?
CVE-2021-23018 may allow unauthorized access to sensitive information as communication within the cluster is not secured.
Which versions are affected by CVE-2021-23018?
CVE-2021-23018 affects F5 NGINX Controller versions from 3.0.0 to prior to 3.4.0.
Is there a workaround for CVE-2021-23018?
There are no recommended workarounds for CVE-2021-23018; the best course of action is to update to an unaffected version.