In Kubernetes clusters using a logging level of at least 4, processing a malformed docker config file will result in the contents of the docker config file being leaked, which can include pull secrets or other registry credentials. This affects < v1.19.3, < v1.18.10, < v1.17.13.
Metrics
Affected Vendors & Products
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2023-0668 | In Kubernetes clusters using a logging level of at least 4, processing a malformed docker config file will result in the contents of the docker config file being leaked, which can include pull secrets or other registry credentials. This affects < v1.19.3, < v1.18.10, < v1.17.13. |
Github GHSA |
GHSA-8mjg-8c8g-6h85 | Kubernetes Sensitive Information leak via Log File |
Fixes
Solution
No solution given by the vendor.
Workaround
Do not enable verbose logging in production (log level >= 4), limit access to logs.
References
History
No history.
Status: PUBLISHED
Assigner: kubernetes
Published:
Updated: 2024-09-16T17:32:40.199Z
Reserved: 2020-02-03T00:00:00
Link: CVE-2020-8564
No data.
Status : Modified
Published: 2020-12-07T22:15:21.307
Modified: 2024-11-21T05:39:02.430
Link: CVE-2020-8564
OpenCVE Enrichment
No data.
EUVD
Github GHSA