RHSA-2020:0975
Vulnerability from csaf_redhat - Published: 2020-03-25 22:42 - Updated: 2026-03-18 02:05A hard-coded cryptographic key vulnerability in the default configuration file was found in Kiali. 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.
| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: 7Server-RH7-RHOSSM-1.0:openshift-service-mesh/kiali-rhel7-operator@sha256:34da7505a15f2bfd5f17bdc46989cd2fea11d22fee8a834b8e2247dd8d63ae72_amd64 | — |
Vendor Fix
fix
Workaround
|
{
"document": {
"aggregate_severity": {
"namespace": "https://access.redhat.com/security/updates/classification/",
"text": "Moderate"
},
"category": "csaf_security_advisory",
"csaf_version": "2.0",
"distribution": {
"text": "Copyright \u00a9 Red Hat, Inc. All rights reserved.",
"tlp": {
"label": "WHITE",
"url": "https://www.first.org/tlp/"
}
},
"lang": "en",
"notes": [
{
"category": "summary",
"text": "An update for openshift-istio-kiali-rhel7-operator-container is now available for Openshift Service Mesh 1.0.\n\nRed Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.",
"title": "Topic"
},
{
"category": "general",
"text": "Red Hat OpenShift Service Mesh is Red Hat\u0027s distribution of the Istio service mesh project, tailored for installation into an on-premise OpenShift Container Platform installation.\n\nSecurity Fix(es):\n\n* kiali: JWT cookie uses default signing key (CVE-2020-1764)\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.",
"title": "Details"
},
{
"category": "legal_disclaimer",
"text": "This content is licensed under the Creative Commons Attribution 4.0 International License (https://creativecommons.org/licenses/by/4.0/). If you distribute this content, or a modified version of it, you must provide attribution to Red Hat Inc. and provide a link to the original.",
"title": "Terms of Use"
}
],
"publisher": {
"category": "vendor",
"contact_details": "https://access.redhat.com/security/team/contact/",
"issuing_authority": "Red Hat Product Security is responsible for vulnerability handling across all Red Hat products and services.",
"name": "Red Hat Product Security",
"namespace": "https://www.redhat.com"
},
"references": [
{
"category": "self",
"summary": "https://access.redhat.com/errata/RHSA-2020:0975",
"url": "https://access.redhat.com/errata/RHSA-2020:0975"
},
{
"category": "external",
"summary": "https://access.redhat.com/security/updates/classification/#moderate",
"url": "https://access.redhat.com/security/updates/classification/#moderate"
},
{
"category": "external",
"summary": "1810383",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=1810383"
},
{
"category": "self",
"summary": "Canonical URL",
"url": "https://security.access.redhat.com/data/csaf/v2/advisories/2020/rhsa-2020_0975.json"
}
],
"title": "Red Hat Security Advisory: Red Hat OpenShift Service Mesh 1.0.10 openshift-istio-kiali-rhel7-operator-container security update",
"tracking": {
"current_release_date": "2026-03-18T02:05:44+00:00",
"generator": {
"date": "2026-03-18T02:05:44+00:00",
"engine": {
"name": "Red Hat SDEngine",
"version": "4.7.3"
}
},
"id": "RHSA-2020:0975",
"initial_release_date": "2020-03-25T22:42:26+00:00",
"revision_history": [
{
"date": "2020-03-25T22:42:26+00:00",
"number": "1",
"summary": "Initial version"
},
{
"date": "2020-03-25T22:42:26+00:00",
"number": "2",
"summary": "Last updated version"
},
{
"date": "2026-03-18T02:05:44+00:00",
"number": "3",
"summary": "Last generated version"
}
],
"status": "final",
"version": "3"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"branches": [
{
"category": "product_name",
"name": "Red Hat OpenShift Service Mesh 1.0",
"product": {
"name": "Red Hat OpenShift Service Mesh 1.0",
"product_id": "7Server-RH7-RHOSSM-1.0",
"product_identification_helper": {
"cpe": "cpe:/a:redhat:service_mesh:1.0::el7"
}
}
}
],
"category": "product_family",
"name": "Red Hat OpenShift Service Mesh"
},
{
"branches": [
{
"category": "product_version",
"name": "openshift-service-mesh/kiali-rhel7-operator@sha256:34da7505a15f2bfd5f17bdc46989cd2fea11d22fee8a834b8e2247dd8d63ae72_amd64",
"product": {
"name": "openshift-service-mesh/kiali-rhel7-operator@sha256:34da7505a15f2bfd5f17bdc46989cd2fea11d22fee8a834b8e2247dd8d63ae72_amd64",
"product_id": "openshift-service-mesh/kiali-rhel7-operator@sha256:34da7505a15f2bfd5f17bdc46989cd2fea11d22fee8a834b8e2247dd8d63ae72_amd64",
"product_identification_helper": {
"purl": "pkg:oci/kiali-rhel7-operator@sha256:34da7505a15f2bfd5f17bdc46989cd2fea11d22fee8a834b8e2247dd8d63ae72?arch=amd64\u0026repository_url=registry.redhat.io/openshift-service-mesh/kiali-rhel7-operator\u0026tag=1.0.12-2"
}
}
}
],
"category": "architecture",
"name": "amd64"
}
],
"category": "vendor",
"name": "Red Hat"
}
],
"relationships": [
{
"category": "default_component_of",
"full_product_name": {
"name": "openshift-service-mesh/kiali-rhel7-operator@sha256:34da7505a15f2bfd5f17bdc46989cd2fea11d22fee8a834b8e2247dd8d63ae72_amd64 as a component of Red Hat OpenShift Service Mesh 1.0",
"product_id": "7Server-RH7-RHOSSM-1.0:openshift-service-mesh/kiali-rhel7-operator@sha256:34da7505a15f2bfd5f17bdc46989cd2fea11d22fee8a834b8e2247dd8d63ae72_amd64"
},
"product_reference": "openshift-service-mesh/kiali-rhel7-operator@sha256:34da7505a15f2bfd5f17bdc46989cd2fea11d22fee8a834b8e2247dd8d63ae72_amd64",
"relates_to_product_reference": "7Server-RH7-RHOSSM-1.0"
}
]
},
"vulnerabilities": [
{
"acknowledgments": [
{
"names": [
"Dagan Henderson"
],
"organization": "Akoya, LLC"
}
],
"cve": "CVE-2020-1764",
"cwe": {
"id": "CWE-321",
"name": "Use of Hard-coded Cryptographic Key"
},
"discovery_date": "2020-03-03T00:00:00+00:00",
"ids": [
{
"system_name": "Red Hat Bugzilla ID",
"text": "1810383"
}
],
"notes": [
{
"category": "description",
"text": "A hard-coded cryptographic key vulnerability in the default configuration file was found in Kiali. 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.",
"title": "Vulnerability description"
},
{
"category": "summary",
"text": "kiali: JWT cookie uses default signing key",
"title": "Vulnerability summary"
},
{
"category": "other",
"text": "If exploited, an attacker can perform all Kiali admin functions via the API including:\n - View the logs of a pod\n - View Istio metrics, tracing etc.\n - Alter Istio routing configurations:\n - Change the pod availability: adding variances to the weighting, i.e. all traffic goes to 1 pod, or 95% of all traffic. \n - Prevent traffic reaching a pod, DoS\n\nWhilst OpenShift ServiceMesh Kiali uses the default signing key for JWT cookies, it also includes an access_token. This token is generated with a successful login and cannot be easily determined. \n\nTo access the Kiali API in this case, a valid session token would need to be captured first and then added to the JWT cookie.",
"title": "Statement"
},
{
"category": "general",
"text": "The CVSS score(s) listed for this vulnerability do not reflect the associated product\u0027s status, and are included for informational purposes to better understand the severity of this vulnerability.",
"title": "CVSS score applicability"
}
],
"product_status": {
"fixed": [
"7Server-RH7-RHOSSM-1.0:openshift-service-mesh/kiali-rhel7-operator@sha256:34da7505a15f2bfd5f17bdc46989cd2fea11d22fee8a834b8e2247dd8d63ae72_amd64"
]
},
"references": [
{
"category": "self",
"summary": "Canonical URL",
"url": "https://access.redhat.com/security/cve/CVE-2020-1764"
},
{
"category": "external",
"summary": "RHBZ#1810383",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=1810383"
},
{
"category": "external",
"summary": "https://www.cve.org/CVERecord?id=CVE-2020-1764",
"url": "https://www.cve.org/CVERecord?id=CVE-2020-1764"
},
{
"category": "external",
"summary": "https://nvd.nist.gov/vuln/detail/CVE-2020-1764",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-1764"
},
{
"category": "external",
"summary": "https://kiali.io/news/security-bulletins/kiali-security-001/",
"url": "https://kiali.io/news/security-bulletins/kiali-security-001/"
}
],
"release_date": "2020-03-25T18:00:00+00:00",
"remediations": [
{
"category": "vendor_fix",
"date": "2020-03-25T22:42:26+00:00",
"details": "The OpenShift Service Mesh release notes provide information on the features and known issues:\n\nhttps://docs.openshift.com/container-platform/4.3/service_mesh/servicemesh-release-notes.html",
"product_ids": [
"7Server-RH7-RHOSSM-1.0:openshift-service-mesh/kiali-rhel7-operator@sha256:34da7505a15f2bfd5f17bdc46989cd2fea11d22fee8a834b8e2247dd8d63ae72_amd64"
],
"restart_required": {
"category": "none"
},
"url": "https://access.redhat.com/errata/RHSA-2020:0975"
},
{
"category": "workaround",
"details": "The Kiali configuration can be manually updated for ServiceMesh so that the default signing_key cannot be easily determined:\n\noc get kiali -n $(oc get kiali --all-namespaces --no-headers -o custom-columns=NS:.metadata.namespace) -o yaml | sed \"s/spec:/spec:\\n login_token:\\n signing_key: $(chars=abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890; for i in {1..20}; do echo -n \"${chars:RANDOM%${#chars}:1}\"; done; echo)/\" | oc apply -f -",
"product_ids": [
"7Server-RH7-RHOSSM-1.0:openshift-service-mesh/kiali-rhel7-operator@sha256:34da7505a15f2bfd5f17bdc46989cd2fea11d22fee8a834b8e2247dd8d63ae72_amd64"
]
}
],
"scores": [
{
"cvss_v3": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.6,
"baseSeverity": "HIGH",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H",
"version": "3.1"
},
"products": [
"7Server-RH7-RHOSSM-1.0:openshift-service-mesh/kiali-rhel7-operator@sha256:34da7505a15f2bfd5f17bdc46989cd2fea11d22fee8a834b8e2247dd8d63ae72_amd64"
]
}
],
"threats": [
{
"category": "impact",
"details": "Moderate"
}
],
"title": "kiali: JWT cookie uses default signing key"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.