dbcve.org
Openshift Service MeshApplication · Redhat

CVE-2020-1762

HIGH · 8.6 CVSS v3.1 Published 2020-04-27
Fix available
A fix is available. Upgrade to 1.15.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable 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
An insufficient JWT validation vulnerability was found in Kiali versions 0.4.0 to 1.15.0 and was fixed in Kiali version 1.15.1, wherein a remote attacker could abuse this flaw by stealing a valid JWT cookie and using that to spoof a user session, possibly gaining privileges to view and alter the Istio configuration.

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

Kiali versions 0.4.0 through 1.15.0 have insufficient JWT validation that allows a remote attacker who obtains a valid JWT cookie to spoof user sessions and potentially gain privileges to view and modify Istio service mesh configuration.

MitigationUpgrade Kiali to version 1.15.1 or later to address the insufficient JWT validation vulnerability.

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
Openshift Service MeshApplication
Affected:= 1.0
KialiApplication
Affected:>= 0.4.0, < 1.15.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
High

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

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 Kiali version
    Check the Kiali deployment version via 'kubectl get deployment -n <istio-system> kiali -o jsonpath={.spec.template.spec.containers[0].image}' or check the Kiali UI footer for version number
    Affected if version is 0.4.0 through 1.15.0 inclusive
  2. Confirm OpenShift Service Mesh usage
    Check if the environment uses Red Hat OpenShift Service Mesh 1.0 by reviewing installed operators or service mesh control plane configuration in the 'istio-system' namespace
    Affected if OpenShift Service Mesh version 1.0 is deployed alongside vulnerable Kiali versions
  3. Verify JWT authentication is enabled
    Inspect Kiali configuration for authentication settings - check the Kiali CR (CustomResource) or ConfigMap for 'auth.strategy' set to 'openid' or 'token' which enables JWT-based authentication
    Affected if JWT/OpenID authentication strategy is configured in Kiali (not disabled or set to 'anonymous')

You are affected if Kiali version is between 0.4.0 and 1.15.0 inclusive AND JWT authentication is enabled, especially in OpenShift Service Mesh 1.0 environments

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.

From vendor data
Upgrade available Upgrade to 1.15.1 or later
Fixed in 1.15.1
Interim mitigation

Upgrade Kiali to version 1.15.1 or later to address the insufficient JWT validation vulnerability.

Fix this in Openshift Service Mesh Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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