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.
The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Kiali | Kiali | * | 1.15.1 (excluding) |
Openshift Service Mesh 1.0 | RedHat | openshift-service-mesh/kiali-rhel7-operator:1.0.12-2 | * |