RHSA-2020:0928: Moderate: OpenShift Container Platform 4.3.8 openshift-clients security update
Red Hat OpenShift Container Platform is Red Hat's cloud computingKubernetes application platform solution designed for on-premise or privatecloud deployments.Security Fix(es): proglottis/gpgme: Use-after-free in GPGME bindings during container image pull (CVE-2020-8945) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/openshift-clientsto a version that resolves this vulnerability.Fixed in 4.3.7-202003130552.git.0.6027a27.el8 - Upgrade
Upgrade
redhat/openshift-clients-redistributableto a version that resolves this vulnerability.Fixed in 4.3.7-202003130552.git.0.6027a27.el8 - Upgrade
Upgrade
redhat/openshift-clientsto a version that resolves this vulnerability.Fixed in 4.3.7-202003130552.git.0.6027a27.el7 - Upgrade
Upgrade
redhat/openshift-clients-redistributableto a version that resolves this vulnerability.Fixed in 4.3.7-202003130552.git.0.6027a27.el7 - Upgrade
Upgrade
OpenShift Container Platformto a version that resolves this vulnerability.Fixed in 4.3.8
Event History
Frequently Asked Questions
What is the severity of RHSA-2020:0928?
The severity of RHSA-2020:0928 is classified as moderate.
How do I fix RHSA-2020:0928?
To fix RHSA-2020:0928, update to the fixed version 4.3.7-202003130552.git.0.6027a27.el8 or 4.3.7-202003130552.git.0.6027a27.el7 depending on your system.
What products are affected by RHSA-2020:0928?
Products affected by RHSA-2020:0928 include Red Hat OpenShift Container Platform versions prior to 4.3.7.
What vulnerability does RHSA-2020:0928 address?
RHSA-2020:0928 addresses a use-after-free vulnerability in GPGME bindings during container image pull.
Is there a workaround for RHSA-2020:0928?
There is no known workaround for RHSA-2020:0928; applying the update is the recommended solution.