CVE-2021-3495: High severity Netlify Kiali-operator vulnerability

Published Apr 8, 2021
·
Updated

An incorrect access control flaw was found in the kiali-operator in versions before 1.33.0 and before 1.24.7. This flaw allows an attacker with a basic level of access to the cluster (to deploy a kiali operand) to use this vulnerability and deploy a given image to anywhere in the cluster, potentially gaining access to privileged service account tokens. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

Other sources

If you create a kiali instance, then you can specify any project in yaml and it will be installed there, ignoring the rights to this project. If current user has edit permissions to 'user-namespace' but not to 'any-namespace', kiali anyway will be created in 'any-namespace'.

Reference:

https://issues.redhat.com/browse/KIALI-3278

Red Hat

Affected Software

6 affected componentsFixes available
redhat/kiali/kiali-operator<1.33.0
1.33.0
redhat/kiali/kiali-operator<1.24.7
1.24.7
Netlify Kiali-operator<1.24.7
Netlify Kiali-operator>=1.30.0<1.33.0
redhat Openshift Service Mesh=1.0
redhat Openshift Service Mesh=2.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/kiali/kiali-operator to a version that resolves this vulnerability.

    Fixed in 1.33.0
  2. Upgrade

    Upgrade redhat/kiali/kiali-operator to a version that resolves this vulnerability.

    Fixed in 1.24.7
  3. Upgrade

    Upgrade kiali-operator to a version that resolves this vulnerability.

    Fixed in 1.33.0
  4. Upgrade

    Upgrade kiali-operator to a version that resolves this vulnerability.

    Fixed in 1.24.7
  5. Compensating control

    Until upgraded, restrict cluster permissions so that users who can deploy kiali operands cannot edit or deploy into namespaces they should not control (the flaw can allow installation into 'any-namespace' / arbitrary projects by specifying them in YAML).

Event History

Jun 1, 2021
CVE Published
via MITRE·01:31 PM
Data Sourced
via MITRE·01:31 PM
DescriptionWeakness
Data Sourced
via NVD·02:15 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is CVE-2021-3495?

CVE-2021-3495 is an incorrect access control flaw in the kiali-operator.

2

What is the severity of CVE-2021-3495?

CVE-2021-3495 has a severity rating of 8.8 (High).

3

Which software versions are affected by CVE-2021-3495?

CVE-2021-3495 affects Netlify Kiali-operator versions before 1.33.0 and before 1.24.7, as well as Redhat Openshift Service Mesh versions 1.0 and 2.0.

4

How can an attacker exploit CVE-2021-3495?

An attacker with basic level access to the cluster can deploy a kiali operand and use the vulnerability to deploy a given image anywhere in the cluster.

5

Are there any references for CVE-2021-3495?

Yes, you can find more information about CVE-2021-3495 in the following references: [link 1](https://bugzilla.redhat.com/show_bug.cgi?id=1947361) and [link 2](https://kiali.io/news/security-bulletins/kiali-security-003/).

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203