kiali: JWT cookie uses default signing key
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Red Hat | kiali | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Openshift Service Mesh 1.0 | |||
| openshift-service-mesh/kiali-rhel7-operator:1.0.12-2 | cpe:/a:redhat:service_mesh:1.0::el7 | RHSA-2020:0975 | 2020-03-25T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2021-0966 | 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. |
Github GHSA |
GHSA-64rh-r86q-75ff | Hard coded cryptographic key in Kiali |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 3.5% (3.468% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.