REDHAT-BUG-1734615: Medium severity red hat openshift container platform for ibm linuxone vulnerability

Published Jul 31, 2019

Updated

OpenShift Container Platform 4 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.

Upstream Fix:

https://github.com/openshift/library-go/pull/472

Affected Software

1 affected component

Red Hat OpenShift Container Platform

Event History

Jul 31, 2019

Data Sourced

via Red Hat·06:04 AM

DescriptionSeverityAffected Software

Frequently Asked Questions

What is the severity of REDHAT-BUG-1734615?

The severity of REDHAT-BUG-1734615 is considered moderate due to the potential exposure of sensitive data in pod logs.

How do I fix REDHAT-BUG-1734615?

To fix REDHAT-BUG-1734615, ensure that the log level in your operators is set below Debug to prevent sensitive data from being written to logs.

Who is affected by REDHAT-BUG-1734615?

Users of Red Hat OpenShift Container Platform 4 who allow debug logging in their operators are affected by REDHAT-BUG-1734615.

What are the implications of REDHAT-BUG-1734615?

The implications of REDHAT-BUG-1734615 include the risk of low privileged users gaining access to sensitive secret data through pod logs.

Is there a workaround for REDHAT-BUG-1734615?

Yes, a temporary workaround for REDHAT-BUG-1734615 is to restrict the log level configuration to below Debug in your OpenShift operators.