RHSA-2021:0039: Moderate: OpenShift Container Platform 4.6.12 extras and 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): golang: math/big: panic during recursive division of very large numbers (CVE-2020-28362) For more details about the security issue(s), including the impact, a CVSSscore, acknowledgments, and other related information, refer to the CVEpage(s) listed in the References section.This advisory contains the RPM packages for Red Hat OpenShift ContainerPlatform 4.6.12. See the following advisory for the container images forthis release:https://access.redhat.com/errata/RHSA-2021:0037 All OpenShift Container Platform 4.6 users are advised to upgrade to theseupdated packages and images when they are available in the appropriaterelease channel. To check for available updates, use the OpenShift Consoleor the CLI oc command. Instructions for upgrading a cluster are availableathttps://docs.openshift.com/container-platform/4.6/updating/updating-cluster between-minor.html#understanding-upgrade-channelsupdating-cluster-between minor.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of RHSA-2021:0039?
The severity of RHSA-2021:0039 is classified as important due to its potential impact on the stability of applications.
How do I fix RHSA-2021:0039?
To fix RHSA-2021:0039, users should apply the latest security updates provided by Red Hat for the affected components.
What vulnerabilities are addressed in RHSA-2021:0039?
RHSA-2021:0039 addresses a vulnerability in golang related to panic during recursive division of very large numbers, tracked as CVE-2020-28362.
Which versions of Red Hat OpenShift Container Platform are affected by RHSA-2021:0039?
RHSA-2021:0039 affects multiple versions of Red Hat OpenShift Container Platform that use the vulnerable golang library.
Is there a workaround for RHSA-2021:0039 if I cannot apply the update immediately?
While there are no official workarounds for RHSA-2021:0039, minimizing the use of the vulnerable functions can reduce exposure until an update is applied.