CVE-2020-8563

lowpriority · track · 22EPSS 0.005 · 45 %ileEUUS

grimoire priorityP3 · Track

Exploitable?

—

no known exploitation

Likely / severe?

0.54% (45th) EPSS

CVSS 2.1 · low

Is it mine?

45 products

Check your exposure

Who says so?

5 sources

cnnvd · enisa_euvd · osv · nvd

EPSS · scored 2026-10-27

In Kubernetes clusters using VSphere as a cloud provider, with a logging level set to 4 or above, VSphere cloud credentials will be leaked in the cloud controller manager's log. This affects < v1.19.3.

remediations

Vendor fix, mitigation, or workaround guidance, as published by each source.

A vendor fix is available.

Fixedopenshift-0:4.6.0-202012051246.p0.git.94231.efc9027.el7.src as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
For OpenShift Container Platform 4.6 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/4.6/release_notes/ocp-4-6-release-notes.html Details on how to access this content are available at https://docs.openshift.com/container-platform/4.6/updating/updating-cluster-cli.html.
https://access.redhat.com/errata/RHSA-2020:5260
Fixedopenshift-0:4.6.0-202012051246.p0.git.94231.efc9027.el8.src as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
For OpenShift Container Platform 4.6 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/4.6/release_notes/ocp-4-6-release-notes.html Details on how to access this content are available at https://docs.openshift.com/container-platform/4.6/updating/updating-cluster-cli.html.
https://access.redhat.com/errata/RHSA-2020:5260
Fixedopenshift-hyperkube-0:4.6.0-202012051246.p0.git.94231.efc9027.el7.x86_64 as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
For OpenShift Container Platform 4.6 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/4.6/release_notes/ocp-4-6-release-notes.html Details on how to access this content are available at https://docs.openshift.com/container-platform/4.6/updating/updating-cluster-cli.html.
https://access.redhat.com/errata/RHSA-2020:5260
Fixedopenshift-hyperkube-0:4.6.0-202012051246.p0.git.94231.efc9027.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
For OpenShift Container Platform 4.6 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/4.6/release_notes/ocp-4-6-release-notes.html Details on how to access this content are available at https://docs.openshift.com/container-platform/4.6/updating/updating-cluster-cli.html.
https://access.redhat.com/errata/RHSA-2020:5260
Fixedopenshift-hyperkube-0:4.6.0-202012051246.p0.git.94231.efc9027.el8.s390x as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
For OpenShift Container Platform 4.6 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/4.6/release_notes/ocp-4-6-release-notes.html Details on how to access this content are available at https://docs.openshift.com/container-platform/4.6/updating/updating-cluster-cli.html.
https://access.redhat.com/errata/RHSA-2020:5260
Fixedopenshift-hyperkube-0:4.6.0-202012051246.p0.git.94231.efc9027.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
For OpenShift Container Platform 4.6 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/4.6/release_notes/ocp-4-6-release-notes.html Details on how to access this content are available at https://docs.openshift.com/container-platform/4.6/updating/updating-cluster-cli.html.
https://access.redhat.com/errata/RHSA-2020:5260
Workaroundcri-o-0:1.19.0-26.rhaos4.6.git8a05a29.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundcri-o-0:1.19.0-26.rhaos4.6.git8a05a29.el8.s390x as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundcri-o-0:1.19.0-26.rhaos4.6.git8a05a29.el8.src as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundcri-o-0:1.19.0-26.rhaos4.6.git8a05a29.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundcri-o-debuginfo-0:1.19.0-26.rhaos4.6.git8a05a29.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundcri-o-debuginfo-0:1.19.0-26.rhaos4.6.git8a05a29.el8.s390x as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundcri-o-debuginfo-0:1.19.0-26.rhaos4.6.git8a05a29.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundcri-o-debugsource-0:1.19.0-26.rhaos4.6.git8a05a29.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundcri-o-debugsource-0:1.19.0-26.rhaos4.6.git8a05a29.el8.s390x as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundcri-o-debugsource-0:1.19.0-26.rhaos4.6.git8a05a29.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundironic-images-0:15.1-20201201.1.el8.noarch as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundironic-images-0:15.1-20201201.1.el8.src as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundironic-images-all-0:15.1-20201201.1.el8.noarch as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundironic-images-ipa-ppc64le-0:15.1-20201201.1.el8.noarch as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundironic-images-ipa-x86_64-0:15.1-20201201.1.el8.noarch as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundopenshift-0:4.6.0-202012051246.p0.git.94231.efc9027.el7.src as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundopenshift-0:4.6.0-202012051246.p0.git.94231.efc9027.el8.src as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundopenshift-ansible-0:4.6.0-202011260456.p0.git.0.e7caea2.el7.noarch as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundopenshift-ansible-0:4.6.0-202011260456.p0.git.0.e7caea2.el7.src as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundopenshift-ansible-test-0:4.6.0-202011260456.p0.git.0.e7caea2.el7.noarch as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundopenshift-clients-0:4.6.0-202011260456.p0.git.3798.fcf58ff.el7.src as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundopenshift-clients-0:4.6.0-202011260456.p0.git.3798.fcf58ff.el7.x86_64 as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundopenshift-clients-0:4.6.0-202011260456.p0.git.3798.fcf58ff.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundopenshift-clients-0:4.6.0-202011260456.p0.git.3798.fcf58ff.el8.s390x as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundopenshift-clients-0:4.6.0-202011260456.p0.git.3798.fcf58ff.el8.src as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundopenshift-clients-0:4.6.0-202011260456.p0.git.3798.fcf58ff.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundopenshift-clients-redistributable-0:4.6.0-202011260456.p0.git.3798.fcf58ff.el7.x86_64 as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundopenshift-clients-redistributable-0:4.6.0-202011260456.p0.git.3798.fcf58ff.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundopenshift-hyperkube-0:4.6.0-202012051246.p0.git.94231.efc9027.el7.x86_64 as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundopenshift-hyperkube-0:4.6.0-202012051246.p0.git.94231.efc9027.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundopenshift-hyperkube-0:4.6.0-202012051246.p0.git.94231.efc9027.el8.s390x as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundopenshift-hyperkube-0:4.6.0-202012051246.p0.git.94231.efc9027.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundopenshift-kuryr-0:4.6.0-202012042155.p0.git.2216.8a6f6a5.el8.src as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundopenshift-kuryr-cni-0:4.6.0-202012042155.p0.git.2216.8a6f6a5.el8.noarch as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundopenshift-kuryr-common-0:4.6.0-202012042155.p0.git.2216.8a6f6a5.el8.noarch as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundopenshift-kuryr-controller-0:4.6.0-202012042155.p0.git.2216.8a6f6a5.el8.noarch as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundpython-eventlet-0:0.25.2-3.el8ost.src as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundpython-pyroute2-0:0.5.13-1.el8ost.src as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundpython3-eventlet-0:0.25.2-3.el8ost.noarch as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundpython3-kuryr-kubernetes-0:4.6.0-202012042155.p0.git.2216.8a6f6a5.el8.noarch as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.
Workaroundpython3-pyroute2-0:0.5.13-1.el8ost.noarch as a component of Red Hat OpenShift Container Platform 4.6redhat_csaf
Ensure that the logging level is below 4. Additionally, protect unauthorized access to cluster logs. For OCP, the logging level for core components can be configured using operators, e.g. for kube-controller-manager: https://docs.openshift.com/container-platform/latest/rest_api/operator_apis/kubecontrollermanager-operator-openshift-io-v1.html#specification In OCP, a logging level of "Debug" is equivalent to 4: https://github.com/openshift/api/blob/master/operator/v1/types.go#L96 The default logging level is "Normal", which is equivalent to 2. Clusters running with the default level are not vulnerable to this issue.

cvss

Technical severity, 0–10. One row per scoring source.

6.3

010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · low–medium · 2.1–6.3

v2.02.1lowAV:L/AC:L/Au:N/C:P/I:N/A:Nprimary · NVD / NIST USexploitability 3.9 · impact 2.9

v3.15.5mediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:Nprimary · NVD / NIST USexploitability 1.8 · impact 3.6

v3.14.7mediumCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:Nsecondary · ENISA EU

v3.14.7mediumCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:Nsecondary · jordan@liggitt.netexploitability 1 · impact 3.6

v3.16.3mediumCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:Nsecondary · OSV

v3.15.1mediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N/E:Usecondary · CVSS-BT (t0sche)

v3.16.3mediumCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:Nsecondary · Red Hat Product Security US

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-532USprimaryCWE-117USCWE-532US

affected products (45)

Products and version ranges known to be affected.

Kubernetes Kubernetes≤ < 1.19.3enisa_euvdEU
kubernetes kubernetes< 1.19.3nvdUScpe:2.3:a:kubernetes:kubernetes:*:*:*:*:*:*:*:*
Go github.com/kubernetes/kubernetes< 1.19.3osvUSpkg:golang/github.com/kubernetes/kubernetes
Go k8s.io/kubernetes< 1.19.3osvUSpkg:golang/k8s.io/kubernetes
cri-o-0:1.19.0-26.rhaos4.6.git8a05a29.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.6all versionsnot affectedredhat_csafUS
cri-o-0:1.19.0-26.rhaos4.6.git8a05a29.el8.s390x as a component of Red Hat OpenShift Container Platform 4.6all versionsnot affectedredhat_csafUS
cri-o-0:1.19.0-26.rhaos4.6.git8a05a29.el8.src as a component of Red Hat OpenShift Container Platform 4.6all versionsnot affectedredhat_csafUS
cri-o-0:1.19.0-26.rhaos4.6.git8a05a29.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.6all versionsnot affectedredhat_csafUS
cri-o-debuginfo-0:1.19.0-26.rhaos4.6.git8a05a29.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.6all versionsnot affectedredhat_csafUS
cri-o-debuginfo-0:1.19.0-26.rhaos4.6.git8a05a29.el8.s390x as a component of Red Hat OpenShift Container Platform 4.6all versionsnot affectedredhat_csafUS
cri-o-debuginfo-0:1.19.0-26.rhaos4.6.git8a05a29.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.6all versionsnot affectedredhat_csafUS
cri-o-debugsource-0:1.19.0-26.rhaos4.6.git8a05a29.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.6all versionsnot affectedredhat_csafUS
cri-o-debugsource-0:1.19.0-26.rhaos4.6.git8a05a29.el8.s390x as a component of Red Hat OpenShift Container Platform 4.6all versionsnot affectedredhat_csafUS
cri-o-debugsource-0:1.19.0-26.rhaos4.6.git8a05a29.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.6all versionsnot affectedredhat_csafUS
ironic-images-0:15.1-20201201.1.el8.noarch as a component of Red Hat OpenShift Container Platform 4.6all versionsnot affectedredhat_csafUS
ironic-images-0:15.1-20201201.1.el8.src as a component of Red Hat OpenShift Container Platform 4.6all versionsnot affectedredhat_csafUS
ironic-images-all-0:15.1-20201201.1.el8.noarch as a component of Red Hat OpenShift Container Platform 4.6all versionsnot affectedredhat_csafUS
ironic-images-ipa-ppc64le-0:15.1-20201201.1.el8.noarch as a component of Red Hat OpenShift Container Platform 4.6all versionsnot affectedredhat_csafUS
ironic-images-ipa-x86_64-0:15.1-20201201.1.el8.noarch as a component of Red Hat OpenShift Container Platform 4.6all versionsnot affectedredhat_csafUS
openshift-0:4.6.0-202012051246.p0.git.94231.efc9027.el7.src as a component of Red Hat OpenShift Container Platform 4.6all versionsfixedredhat_csafUS

showing 20 of 45

advisories (3)

Vendor and ecosystem advisories describing this.

RHSA-2020:5260Red Hat Security Advisory: OpenShift Container Platform 4.6.8 security and packages update2020-12-14csaf · redhat_csafUS
Red Hat OpenShift Container Platform release 4.6.8 is now available with updates to packages and images that fix several bugs. An update for ironic-images, openshift, openshift-ansible, openshift-clients, and python-eventlet, cri-o, openshift-kuryr, python-pyroute2 is now available for Red Hat OpenShift Container Platform 4.6. This release also includes a security update for for Red Hat OpenShift Container Platform 4.6. Red 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.
GHSA-5xfg-wv98-264mSensitive Information leak via Log File in Kubernetes2024-04-24ghsa · osvUS
In Kubernetes clusters using VSphere as a cloud provider, with a logging level set to 4 or above, VSphere cloud credentials will be leaked in the cloud controller manager's log. This affects < v1.19.3.
GO-2024-2755Sensitive Information leak for VSphere users via Log File in k8s.io/kubernetes2024-06-05vendor · osvUS
Sensitive Information leak for VSphere users via Log File in k8s.io/kubernetes

also known as (5)

Other names and identifiers for this entity.

sources

Which sources assert this record, and when.

cnnvd enisa_euvd osv nvd redhat_csaf NVD CVE.org MITRE

published 2020-12-07modified 2026-06-17

related (1,489)

Related entries.

ID	severity	EPSS	exploitable	published
CVE-2025-24984US	—OT critical	1.99% (81st)	KEV	2025-03-11
Insertion of sensitive information into log file in Windows NTFS allows an unauthorized attacker to disclose information with a physical attack.
CVE-2023-21492US	medium4.4OT critical	2.55% (85th)	KEV	2023-05-04
Kernel pointers are printed in the log file prior to SMR May-2023 Release 1 allows a privileged local attacker to bypass ASLR.
CVE-2023-43261US	high7.5	63.7% (99th)	Exploit	2023-10-04
An information disclosure in Milesight UR5X, UR32L, UR32, UR35, UR41 before v35.3.0.7 allows attackers to access sensitive router components.
CVE-2022-47075US	high7.5	59.4% (99th)	Exploit	2023-02-28
An issue was discovered in Smart Office Web 20.28 and earlier allows attackers to download sensitive information via the action name parameter to ExportEmployeeDetails.aspx, and to…
CVE-2020-35234US	high7.5	60.4% (99th)	Exploit	2020-12-14
The easy-wp-smtp plugin before 1.4.4 for WordPress allows Administrator account takeover, as exploited in the wild in December 2020. If an attacker can list the wp-content/plugins/…

+1484 more

references (17)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan