dbcve.org
Nginx Service MeshWeb server / proxy · F5

CVE-2022-27495

MEDIUM · 6.5 CVSS v3.1 Published 2022-05-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
On all versions 1.3.x (fixed in 1.4.0) NGINX Service Mesh control plane endpoints are exposed to the cluster overlay network. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

NGINX Service Mesh 1.3.x exposes its control plane endpoints to the entire cluster overlay network, allowing any pod or service within the cluster to potentially reach and interact with the control plane APIs. This increases the attack surface by removing network isolation that should exist between the control plane and workloads.

MitigationUpgrade to NGINX Service Mesh 1.4.0 or later. Alternatively, implement Kubernetes NetworkPolicies to restrict pod-to-control-plane communication to only authorized namespaces or workloads.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Nginx Service MeshWeb server / proxy
Affected:= 1.3.0= 1.3.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify NGINX Service Mesh is installed
    Run 'kubectl get pods -n nginx-mesh' to check for nginx-mesh controller pods, or run 'kubectl get namespaces' to see if 'nginx-mesh' namespace exists
    Affected if NGINX Service Mesh is deployed in the cluster and no NetworkPolicy is restricting access to the control plane
  2. Check installed NGINX Service Mesh version
    Run 'kubectl get pods -n nginx-mesh -o jsonpath="{.items[0].spec.containers[0].image}"' to retrieve the container image tag, or check the helm release if deployed via Helm with 'helm list -n nginx-mesh'
    Affected if The version shown is 1.3.0 or 1.3.1
  3. Inspect control plane service exposure
    Run 'kubectl get svc -n nginx-mesh' to list control plane services, then check their clusterIP or externalIPs. Also run 'kubectl get pods -n nginx-mesh -o wide' to see pod network assignments
    Affected if The control plane services have ClusterIP accessible to all pods in the overlay network without restrictions
  4. Verify NetworkPolicy presence
    Run 'kubectl get networkpolicies -n nginx-mesh' to check if any NetworkPolicies exist restricting pod-to-control-plane traffic
    Affected if No NetworkPolicies are defined in the nginx-mesh namespace to restrict access to the control plane APIs

If NGINX Service Mesh versions 1.3.0 or 1.3.1 are installed with no NetworkPolicy restricting access, the control plane is exposed to all pods in the cluster overlay network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to NGINX Service Mesh 1.4.0 or later. Alternatively, implement Kubernetes NetworkPolicies to restrict pod-to-control-plane communication to only authorized namespaces or workloads.

Recommended fix High confidence

1.4.0

  1. 1. Back up your current NGINX Service Mesh configuration and any custom resources
  2. 2. Ensure you have a snapshot or backup of your cluster state before proceeding
  3. 3. Download NGINX Service Mesh version 1.4.0 from the official F5/NGINX distribution channel
  4. 4. Upgrade the NGINX Service Mesh installation to version 1.4.0 using the appropriate deployment method (e.g., helm upgrade or kubectl apply)
  5. 5. Verify that the control plane endpoints are no longer exposed to the cluster overlay network without authentication
  6. 6. Confirm that authentication is now required for accessing control plane endpoints
  7. 7. Test that existing workloads continue to function correctly after the upgrade
Caveat Review the 1.4.0 release notes for any configuration changes or breaking changes between 1.3.x and 1.4.0 before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nginx Service Mesh Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-27495 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-27495 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data