RHSA-2020:5635: Moderate: OpenShift Container Platform 4.7.0 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): jackson-databind: Serialization gadgets in com.pastdev.httpcomponents.configuration.JndiConfiguration (CVE-2020-24750) gogo/protobuf: plugin/unmarshal/unmarshal.go lacks certain index validation (CVE-2021-3121) golang.org/x/text: possibility to trigger an infinite loop in encoding/unicode could lead to crash (CVE-2020-14040) 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.7.0. See the following advisory for the container images forthis release:https://access.redhat.com/errata/RHEA-2020:5633 All OpenShift Container Platform 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.7/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-2020:5635?
The severity of RHSA-2020:5635 is classified as critical due to the presence of serialization gadgets in jackson-databind.
How do I fix RHSA-2020:5635?
To fix RHSA-2020:5635, you should update the jackson-databind package to a fixed version as specified in the advisory.
What software is affected by RHSA-2020:5635?
RHSA-2020:5635 affects the Red Hat OpenShift Container Platform when using vulnerable versions of jackson-databind.
What are the potential impacts of not addressing RHSA-2020:5635?
Not addressing RHSA-2020:5635 may lead to remote code execution vulnerabilities and data breaches.
Is there a workaround for RHSA-2020:5635?
There are no recommended workarounds for RHSA-2020:5635; updating to the latest version is strongly advised.