First published: Tue Oct 01 2024(Updated: )
Red Hat OpenShift Container Platform is Red Hat's cloud computing Kubernetes application platform solution designed for on-premise or private cloud deployments.<br>This advisory contains the RPM packages for Red Hat OpenShift Container Platform 4.17.0. See the following advisory for the container images for this release:<br><a href="https://access.redhat.com/errata/RHSA-2024:3718" target="_blank">https://access.redhat.com/errata/RHSA-2024:3718</a> Security Fix(es):<br><li> golang-protobuf: encoding/protojson, internal/encoding/json: infinite</li> loop in protojson.Unmarshal when unmarshaling certain forms of invalid JSON<br>(CVE-2024-24786)<br>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.<br>All OpenShift Container Platform 4.17 users are advised to upgrade to these updated packages and images when they are available in the appropriate release channel. To check for available updates, use the OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at <a href="https://docs.openshift.com/container-platform/4.17/updating/updating_a_cluster/updating-cluster-cli.html" target="_blank">https://docs.openshift.com/container-platform/4.17/updating/updating_a_cluster/updating-cluster-cli.html</a>
Affected Software | Affected Version | How to fix |
---|---|---|
Red Hat OpenShift Container Platform for IBM LinuxONE | =4.17.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of RHSA-2024:3717 is classified as important.
To fix RHSA-2024:3717, update your Red Hat OpenShift Container Platform to version 4.17.1 or later.
RHSA-2024:3717 addresses multiple security vulnerabilities found in Red Hat OpenShift Container Platform.
RHSA-2024:3717 specifically affects Red Hat OpenShift Container Platform version 4.17.0.
Yes, temporarily restricting access to the affected components can serve as a workaround for RHSA-2024:3717.