RHSA-2023:5009HighCVSS 7.5

Red Hat Security Advisory: OpenShift Container Platform 4.14.0 security update

Published
October 31, 2023
Last Modified
August 24, 2026

🔗 CVE IDs covered (15)

CVE-2023-2728 →CVE-2023-3978 →CVE-2023-29409 →CVE-2023-39318 →CVE-2023-39325 →CVE-2022-27664 →CVE-2023-3089 →CVE-2023-29824 →CVE-2023-39319 →CVE-2023-44487 →CVE-2023-3153 →CVE-2023-37788 →CVE-2023-2727 →CVE-2023-39321 →CVE-2023-39322 →

📋 Description

CVE-2022-27664 — golang: net/http: handle server errors after sending GOAWAY CVE-2023-2727 — kube-apiserver: Bypassing policies imposed by the ImagePolicyWebhook admission plugin CVE-2023-2728 — kube-apiserver: Bypassing enforce mountable secrets policy imposed by the ServiceAccount admission plugin CVE-2023-3089 — openshift: OCP & FIPS mode CVE-2023-3153 — ovn: service monitor MAC flow is not rate limited CVE-2023-3978 — golang.org/x/net/html: Cross site scripting CVE-2023-29409 — golang: crypto/tls: slow verification of certificate chains containing large RSA keys CVE-2023-29824 — scipy: use-after-free in Py_FindObjects() function CVE-2023-37788 — goproxy: Denial of service (DoS) via unspecified vectors. CVE-2023-39318 — golang: html/template: improper handling of HTML-like comments within script contexts CVE-2023-39319 — golang: html/template: improper handling of special tags within script contexts CVE-2023-39321 — golang: crypto/tls: panic when processing post-handshake message on QUIC connections CVE-2023-39322 — golang: crypto/tls: lack of a limit on buffered post-handshake CVE-2023-39325 — golang: net/http, x/net/http2: rapid stream resets can cause excessive work (CVE-2023-44487) CVE-2023-44487 — HTTP/2: Multiple HTTP/2 enabled web servers are vulnerable to a DDoS attack (Rapid Reset Attack)

🎯 Affected products200

  • Ironic content for Red Hat OpenShift Container Platform 4.14
  • Red Hat OpenShift Container Platform 4.14
  • afterburn-0:5.4.3-1.rhaos4.14.el9.aarch64 as a component of Red Hat OpenShift Container Platform 4.14
  • afterburn-0:5.4.3-1.rhaos4.14.el9.ppc64le as a component of Red Hat OpenShift Container Platform 4.14
  • afterburn-0:5.4.3-1.rhaos4.14.el9.s390x as a component of Red Hat OpenShift Container Platform 4.14
  • afterburn-0:5.4.3-1.rhaos4.14.el9.x86_64 as a component of Red Hat OpenShift Container Platform 4.14
  • afterburn-debuginfo-0:5.4.3-1.rhaos4.14.el9.aarch64 as a component of Red Hat OpenShift Container Platform 4.14
  • afterburn-debuginfo-0:5.4.3-1.rhaos4.14.el9.ppc64le as a component of Red Hat OpenShift Container Platform 4.14
  • afterburn-debuginfo-0:5.4.3-1.rhaos4.14.el9.s390x as a component of Red Hat OpenShift Container Platform 4.14
  • afterburn-debuginfo-0:5.4.3-1.rhaos4.14.el9.x86_64 as a component of Red Hat OpenShift Container Platform 4.14
  • afterburn-dracut-0:5.4.3-1.rhaos4.14.el9.aarch64 as a component of Red Hat OpenShift Container Platform 4.14
  • afterburn-dracut-0:5.4.3-1.rhaos4.14.el9.ppc64le as a component of Red Hat OpenShift Container Platform 4.14
  • afterburn-dracut-0:5.4.3-1.rhaos4.14.el9.s390x as a component of Red Hat OpenShift Container Platform 4.14
  • afterburn-dracut-0:5.4.3-1.rhaos4.14.el9.x86_64 as a component of Red Hat OpenShift Container Platform 4.14
  • bpftool-0:7.0.0-284.36.1.el9_2.aarch64 as a component of Red Hat OpenShift Container Platform 4.14
  • bpftool-0:7.0.0-284.36.1.el9_2.ppc64le as a component of Red Hat OpenShift Container Platform 4.14
  • bpftool-0:7.0.0-284.36.1.el9_2.s390x as a component of Red Hat OpenShift Container Platform 4.14
  • bpftool-0:7.0.0-284.36.1.el9_2.x86_64 as a component of Red Hat OpenShift Container Platform 4.14
  • bpftool-debuginfo-0:7.0.0-284.36.1.el9_2.aarch64 as a component of Red Hat OpenShift Container Platform 4.14
  • bpftool-debuginfo-0:7.0.0-284.36.1.el9_2.ppc64le as a component of Red Hat OpenShift Container Platform 4.14
  • bpftool-debuginfo-0:7.0.0-284.36.1.el9_2.s390x as a component of Red Hat OpenShift Container Platform 4.14
  • bpftool-debuginfo-0:7.0.0-284.36.1.el9_2.x86_64 as a component of Red Hat OpenShift Container Platform 4.14
  • buildah-1:1.29.1-10.1.rhaos4.14.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.14
  • buildah-1:1.29.1-10.1.rhaos4.14.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.14
  • buildah-1:1.29.1-10.1.rhaos4.14.el8.s390x as a component of Red Hat OpenShift Container Platform 4.14
  • buildah-1:1.29.1-10.1.rhaos4.14.el8.src as a component of Red Hat OpenShift Container Platform 4.14
  • buildah-1:1.29.1-10.1.rhaos4.14.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.14
  • buildah-1:1.29.1-10.1.rhaos4.14.el9.aarch64 as a component of Red Hat OpenShift Container Platform 4.14
  • buildah-1:1.29.1-10.1.rhaos4.14.el9.ppc64le as a component of Red Hat OpenShift Container Platform 4.14
  • buildah-1:1.29.1-10.1.rhaos4.14.el9.s390x as a component of Red Hat OpenShift Container Platform 4.14
  • +170 more not shown

✅ Remediation

For OpenShift Container Platform 4.14 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/4.14/release_notes/ocp-4-14-release-notes.html Workaround: This issue can be mitigated by applying the patch provided for the kube-apiserver component. This patch prevents ephemeral containers from using an image that is restricted by ImagePolicyWebhook. Note: Validation webhooks, (such as Gatekeeper <https://open-policy-agent.github.io/gatekeeper-library/website/validation/allowedrepos> and Kyverno <https://kyverno.io/policies/other/allowed-image-repos/allowed-image-repos/>) can also be used to enforce the same restrictions. Workaround: This issue can be mitigated by applying the patch provided for the kube-apiserver component. The patch prevents ephemeral containers from bypassing the mountable secrets policy enforced by the ServiceAccount admission plugin. Workaround: Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected packages as soon as possible. Workaround: The default stream concurrency limit in golang is 250 streams (requests) per HTTP/2 connection. This value may be adjusted in the golang.org/x/net/http2 package using the Server.MaxConcurrentStreams setting and the ConfigureServer function which are available in golang.org/x/net/http2. Workaround: Users are strongly urged to update their software as soon as fixes are available. There are several mitigation approaches for this flaw. 1. If circumstances permit, users may disable http2 endpoints to circumvent the flaw altogether until a fix is available. 2. IP-based blocking or flood protection and rate control tools may be used at network endpoints to filter incoming traffic. 3. Several package specific mitigations are also available. a. nginx: https://www.nginx.com/blog/http-2-rapid-reset-attack-impacting-f5-nginx-products/ b. netty: https://github.com/netty/netty/security/advisories/GHSA-xpw8-rcwv-8f8p c. haproxy: https://www.haproxy.com/blog/haproxy-is-not-affected-by-the-http-2-rapid-reset-attack-cve-2023-44487 d. nghttp2: https://github.com/nghttp2/nghttp2/security/advisories/GHSA-vx74-f528-fxqg e. golang: The default stream concurrency limit in golang is 250 streams (requests) per HTTP/2 connection. This value may be adjusted in the golang.org/x/net/http2 package using the Server.MaxConcurrentStreams setting and the ConfigureServer function which are available in golang.org/x/net/http2.

🔗 References (17)