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.
Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Kubernetes | Kubernetes | 1.17.0 (including) | 1.17.13 (excluding) |
Kubernetes | Kubernetes | 1.18.0 (including) | 1.18.10 (excluding) |
Kubernetes | Kubernetes | 1.19.0 (including) | 1.19.3 (excluding) |
Red Hat OpenShift Container Platform 3.11 | RedHat | atomic-openshift-0:3.11.501-1.git.0.f8c4746.el7 | * |
Red Hat OpenShift Container Platform 4.4 | RedHat | openshift4/ose-docker-builder:v4.4.0-202101261542.p0 | * |
Red Hat OpenShift Container Platform 4.5 | RedHat | openshift4/ose-docker-builder:v4.5.0-202012050338.p0 | * |
Red Hat OpenShift Container Platform 4.6 | RedHat | openshift-clients-0:4.6.0-202010081244.p0.git.3794.4743d24.el8 | * |
Red Hat OpenShift Container Platform 4.6 | RedHat | openshift-0:4.6.0-202101160934.p0.git.94242.fc5242e.el7 | * |
Red Hat OpenShift Container Platform 4.6 | RedHat | openshift4/ose-docker-builder:v4.6.0-202012050130.p0 | * |
Red Hat OpenShift Container Platform 4.6 | RedHat | openshift4/ose-hyperkube:v4.6.0-202101160934.p0 | * |
Kubernetes | Ubuntu | groovy | * |
Kubernetes | Ubuntu | hirsute | * |
Kubernetes | Ubuntu | impish | * |
Kubernetes | Ubuntu | kinetic | * |
Kubernetes | Ubuntu | lunar | * |
Kubernetes | Ubuntu | mantic | * |
While logging all information may be helpful during development stages, it is important that logging levels be set appropriately before a product ships so that sensitive user data and system information are not accidentally exposed to potential attackers. Different log files may be produced and stored for: