dbcve.org
Nginx Ingress ControllerWeb server / proxy · F5

CVE-2022-30535

MEDIUM · 6.5 CVSS v3.1 Published 2022-08-04
Fix available
A fix is available. Upgrade to 2.3.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
In versions 2.x before 2.3.0 and all versions of 1.x, An attacker authorized to create or update ingress objects can obtain the secrets available to the NGINX Ingress Controller. 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

The NGINX Ingress Controller versions 1.x and 2.x before 2.3.0 contains an authorization flaw where users with permissions to create or update ingress objects can access secrets available to the ingress controller, enabling privilege escalation beyond their intended permissions.

MitigationUpgrade NGINX Ingress Controller to version 2.3.0 or later for 2.x deployments, or apply vendor patches for 1.x versions. Review existing RBAC policies to limit ingress object permissions to only necessary users.

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 Ingress ControllerWeb server / proxy
Affected:>= 1.0.0, < 2.3.0

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Identify if NGINX Ingress Controller is deployed
    Run 'kubectl get deployments -A | grep -i nginx' or 'kubectl get pods -A | grep -i ingress' to find NGINX Ingress Controller pods or deployments in the cluster
    Affected if NGINX Ingress Controller is present in the cluster
  2. Determine the installed NGINX Ingress Controller version
    Run 'kubectl get deployment -n <ingress-namespace> <ingress-controller-deployment> -o jsonpath={.spec.template.spec.containers[0].image}' to get the image and version, or check the Helm chart version if deployed via Helm
    Affected if The version is >= 1.0.0 and < 2.3.0
  3. Check RBAC permissions for ingress object creation or updates
    Run 'kubectl get clusterrolebinding -o yaml | grep -i ingress' or 'kubectl auth can-i create ingresses --as=<user>' to identify which users or service accounts have permissions to create or update Ingress resources
    Affected if Users or service accounts other than cluster-admin have ingress create/update permissions
  4. Verify if ingress objects with secret references exist
    Run 'kubectl get ingress -A -o jsonpath={range .items[*]}{.metadata.namespace}{.metadata.name}{.spec.tls}{.spec.rules}{end}' to check for Ingress resources that reference TLS secrets or use backend services that may access secrets
    Affected if Ingress resources exist that could potentially access secrets in namespaces accessible to the ingress controller

A user is affected if NGINX Ingress Controller version is >= 1.0.0 and < 2.3.0 AND non-admin users have permissions to create or update Ingress objects in the cluster.

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
Upgrade available Upgrade to 2.3.0 or later
Fixed in 2.3.0
Interim mitigation

Upgrade NGINX Ingress Controller to version 2.3.0 or later for 2.x deployments, or apply vendor patches for 1.x versions. Review existing RBAC policies to limit ingress object permissions to only necessary users.

Recommended fix High confidence

Nginx Ingress Controller 2.3.0 or later (or the latest stable 2.x release)

  1. 1. Review the Nginx Ingress Controller upgrade documentation for your deployment method (Helm, YAML manifests, etc.)
  2. 2. Create a backup of your current Nginx Ingress Controller configuration and any custom resources
  3. 3. If using Helm, update the Helm chart repository: helm repo update
  4. 4. Upgrade Nginx Ingress Controller to version 2.3.0 or later. For Helm: helm upgrade <release-name> nginx-stable/nginx-ingress --version 2.3.0 or later
  5. 5. For YAML manifests, apply the new manifests from the 2.3.0 release
  6. 6. Verify the upgrade was successful by checking the controller pod is running and there are no errors in the logs
  7. 7. Confirm the ingress controller can still route traffic correctly
Caveat Upgrading from 1.x to 2.x may have breaking changes; review the 2.x migration guide before upgrading if currently on 1.x

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

Fix this in Nginx Ingress Controller Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-30535 — 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-30535 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