Skip to content
Fencer Vulns
high 8.6

CVE-2020-1764 json

Hard coded cryptographic key in Kiali

published 2020-03-26 6 y ago modified 2026-06-17 4 mo ago also GHSA-64rh-r86q-75ff , GO-2022-0631 , EUVD-2021-0966

cvss
8.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
3.5%
EPSS 3.5% chance of exploitation in 30 days, percentile 89%
public exploits
0
none known

Summary

A hard-coded cryptographic key vulnerability in the default configuration file was found in Kiali, all versions prior to 1.15.1. A remote attacker could abuse this flaw by creating their own JWT signed tokens and bypass Kiali authentication mechanisms, possibly gaining privileges to view and alter the Istio configuration.

Patch / fix

  • go github.com/kiali/kiali 1.15.1
  • kiali kiali 1.15.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-1764 updated cvss 8.6

kiali: JWT cookie uses default signing key

  • Red Hat OpenShift Service Mesh 1.0 openshift-service-mesh/kiali-rhel7-operator 1.0.12-2
    fixed: vendor fix RHSA-2020:0975

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.47% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • kiali.io https://kiali.io/news/security-bulletins/kiali-security-001/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
NVD 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.0 8.6 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

Affected packages

ecosystem package affected fixed in
go github.com/kiali/kiali
<1.15.1
1.15.1

Affected products

  • Red Hat kiali

Classification

Weakness
  • CWE-321 Use of Hard-coded Cryptographic Key
  • CWE-798 Use of Hard-coded Credentials

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.