OpenShift Container Platform, versions 4.1 and 4.2, does not sanitize secret data written to pod logs when the log level in a given operator is set to Debug or higher. A low privileged user could read pod logs to discover secret material if the log level has already been modified in an operator by a privileged user.
The product does not neutralize or incorrectly neutralizes output that is written to logs.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Openshift_container_platform | Redhat | 4.1 (including) | 4.1 (including) |
Openshift_container_platform | Redhat | 4.2 (including) | 4.2 (including) |
Red Hat OpenShift Container Platform 4.1 | RedHat | openshift4/ose-console-operator:v4.1.16-201909100604 | * |
Red Hat OpenShift Container Platform 4.1 | RedHat | openshift4/ose-cluster-authentication-operator:v4.1.26-201911260202 | * |
Red Hat OpenShift Container Platform 4.1 | RedHat | openshift4/ose-cluster-config-operator:v4.1.26-201911260202 | * |
Red Hat OpenShift Container Platform 4.1 | RedHat | openshift4/ose-cluster-kube-apiserver-operator:v4.1.26-201911260202 | * |
Red Hat OpenShift Container Platform 4.1 | RedHat | openshift4/ose-cluster-openshift-apiserver-operator:v4.1.27-201912030019 | * |
This can allow an attacker to forge log entries or inject malicious content into logs. Log forging vulnerabilities occur when: