Secret leaks in logs for vSphere Provider kube-controller-manager
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Kubernetes | Kubernetes | affected |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat OpenShift Container Platform 4.6 | |||
| openshift-0:4.6.0-202012051246.p0.git.94231.efc9027.el7 | cpe:/a:redhat:openshift:4.6::el7 | RHSA-2020:5260 | 2020-12-14T00:00:00Z |
| Red Hat OpenShift Container Platform 4.7 | |||
| openshift4/ose-hyperkube:v4.7.0-202102130115.p0 | cpe:/a:redhat:openshift:4.7::el8 | RHSA-2020:5633 | 2021-02-24T00:00:00Z |
No data available yet.
Vendor Workaround
Do not enable verbose logging in production (log level >= 4), limit access to logs.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-1110 | 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. |
Github GHSA |
GHSA-5xfg-wv98-264m | Sensitive Information leak via Log File in Kubernetes |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.539% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.