LiveActive security incident?Get immediate response
CVE Record

CVE-2021-23018: Intra-cluster communication does not use TLS.

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

NGINX Controller 3.x before 3.4.0 used unencrypted communication between services inside its cluster namespace. That can expose sensitive internal traffic if an attacker or unauthorized user can observe traffic inside the cluster. The source bundle does not show internet-facing exploitation or a CVSS score.

Executive priority

Treat this as a contained but important internal infrastructure risk. Prioritize remediation if NGINX Controller is deployed in production clusters, especially where cluster compromise would expose credentials, control-plane data, or operational traffic.

Technical view

CVE-2021-23018 is a CWE-319 cleartext transmission issue in NGINX Controller. Services within the Controller 3.x namespace used cleartext protocols for intra-cluster communication before version 3.4.0. The practical risk depends on cluster network access, namespace isolation, and whether an attacker can intercept internal service traffic.

Likely exposure

Exposure is limited to environments running NGINX Controller 3.x before 3.4.0. Risk is most relevant where cluster networking or namespace access is weakly controlled, or where another compromise could enable internal traffic observation.

Exploitation context

The source bundle does not report active exploitation, and KEV is false. Exploitation would require a position where intra-cluster traffic can be observed or intercepted; the bundle does not provide public exploit evidence.

Researcher notes

Evidence is narrow: the bundle identifies affected versions, cleartext intra-cluster communication, CWE-319, and the F5 advisory. It does not include CVSS, detailed technical root cause, proof-of-concept status, or specific compensating controls beyond leaving the affected version range.

Mitigation direction

  • Identify any NGINX Controller deployments and record their versions.
  • Upgrade affected 3.x deployments to 3.4.0 or later per F5 guidance.
  • Review the F5 advisory for product-specific remediation details.
  • Restrict access to the Controller namespace and cluster network paths.
  • Monitor for unauthorized cluster access or suspicious internal traffic observation.

Validation and detection

  • Confirm no NGINX Controller 3.x deployment remains below 3.4.0.
  • Verify Controller services are no longer using cleartext intra-cluster communication.
  • Review namespace access controls and pod-to-pod network restrictions.
  • Check change records for remediation against all affected clusters.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-319: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-23018 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aNginx Controller"3.x before 3.4.0"Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-319 · source CWE mapping

Cleartext Transmission of Sensitive Information

Cleartext Transmission of Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.