IstioApplication

CVE-2022-21701

HIGH · 8.8 CVSS v3.1 Published 2022-01-19

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

94/100

Remediation priority · Urgent

Remotely reachable Zero-click

Official description

NVD · unedited

Istio is an open platform to connect, manage, and secure microservices. In versions 1.12.0 and 1.12.1 Istio is vulnerable to a privilege escalation attack. Users who have `CREATE` permission for `gateways.gateway.networking.k8s.io` objects can escalate this privilege to create other resources that they may not have access to, such as `Pod`. This vulnerability impacts only an Alpha level feature, the Kubernetes Gateway API. This is not the same as the Istio Gateway type (gateways.networking.istio.io), which is not vulnerable. Users are advised to upgrade to resolve this issue. Users unable to upgrade should implement any of the following which will prevent this vulnerability: Remove the gateways.gateway.networking.k8s.io CustomResourceDefinition, set PILOT_ENABLE_GATEWAY_API_DEPLOYMENT_CONTROLLER=true environment variable in Istiod, or remove CREATE permissions for gateways.gateway.networking.k8s.io objects from untrusted users.

Technical summary

dbcve analysis · high confidence

Istio 1.12.0 and 1.12.1 contain a privilege escalation vulnerability in the Alpha-level Kubernetes Gateway API integration. Users with CREATE permission on gateways.gateway.networking.k8s.io resources can escalate to create other resources like Pods that they may not have permission to access. This only affects the Kubernetes Gateway API (gateways.gateway.networking.k8s.io), not the standard Istio Gateway type (gateways.networking.istio.io).

MitigationUpgrade Istio to version 1.12.2 or later. Alternatively, remove the gateways.gateway.networking.k8s.io CRD, set PILOT_ENABLE_GATEWAY_API_DEPLOYMENT_CONTROLLER=false in Istiod, or restrict CREATE permissions on the Gateway API gateway resource for untrusted users.

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

Affected products & versions

NVD · CPE data

IstioApplication

Affected:= 1.12.0= 1.12.1

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: Low
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

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

Am I affected?

dbcve checks

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

Check installed Istio version

Run 'istioctl version' or check the Istiod container image tag

Affected if Version is 1.12.0 or 1.12.1
Verify Kubernetes Gateway API CRD exists

Run 'kubectl get crd gateways.gateway.networking.k8s.io' to confirm the CRD is present

Affected if The CRD exists in the cluster
Confirm Gateway API deployment controller is enabled

Check Istiod deployment environment variables or run 'istioctl get meshconfig' to see if PILOT_ENABLE_GATEWAY_API_DEPLOYMENT_CONTROLLER is set to true (default is true for affected versions)

Affected if PILOT_ENABLE_GATEWAY_API_DEPLOYMENT_CONTROLLER is not explicitly set to false
Check for CREATE permissions on Gateway API gateway resources

Run 'kubectl auth can-i create gateways.gateway.networking.k8s.io' as the user in question, or review RBAC policies for the gateways.gateway.networking.k8s.io resource

Affected if Untrusted users have CREATE permission on gateways.gateway.networking.k8s.io

You are affected if you run Istio 1.12.0 or 1.12.1 AND have the Kubernetes Gateway API CRDs installed with the deployment controller enabled AND untrusted users can create gateway.gateway.networking.k8s.io resources.

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

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade Istio to version 1.12.2 or later. Alternatively, remove the gateways.gateway.networking.k8s.io CRD, set PILOT_ENABLE_GATEWAY_API_DEPLOYMENT_CONTROLLER=false in Istiod, or restrict CREATE permissions on the Gateway API gateway resource for untrusted users.

Recommended fix Moderate confidence

Istio 1.12.2 or later

1. Review current Istio installation version using `istioctl version` or checking Istiod deployment
2. Plan for upgrade to Istio version 1.12.2 or later (the next patch release after 1.12.1)
3. Before upgrading, identify users who have CREATE permissions on gateways.gateway.networking.k8s.io resources using `kubectl auth can-i create gateways.gateway.networking.k8s.io --as=<user>`
4. Perform upgrade following standard Istio upgrade procedures: `istioctl upgrade` or via your Kubernetes package manager
5. After upgrade, verify the vulnerability is resolved by confirming Istiod version is 1.12.2 or later
6. Alternatively, if immediate upgrade is not possible, remove the gateways.gateway.networking.k8s.io CRD: `kubectl delete crd gateways.gateway.networking.k8s.io`
7. Or alternatively, set environment variable PILOT_ENABLE_GATEWAY_API_DEPLOYMENT_CONTROLLER=true in Istiod deployment

Caveat Review Istio 1.12.2 release notes for any breaking changes; standard minor version upgrade risks apply (test in staging first)

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

Fix this in Istio 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-21701 — 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

Primary sources

istio.ioMitigationRelease NotesVendor Advisory
github.comThird Party Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2022-21701?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 8.8 High

Exploit likelihood EPSS, next 30 days 0.8%

Affects: Istio

Remediation

A high-priority fix

Fix this in Istio 18 hrs · Moderate

Typical engagement from $3,200

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2022-21701 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References