RHSA-2023:6154HighCVSS 7.5

Red Hat Security Advisory: Secondary Scheduler Operator for Red Hat OpenShift 1.2.0

Published
November 1, 2023
Last Modified
September 22, 2026

🔗 CVE IDs covered (6)

CVE-2023-39322 →CVE-2023-39325 →CVE-2023-44487 →CVE-2023-39318 →CVE-2023-39319 →CVE-2023-39321 →

📋 Description

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 products3

  • OSSO 1.2 for RHEL 8
  • openshift-secondary-scheduler-operator/secondary-scheduler-operator-bundle@sha256:775e1822637d308859c4eff42d7b09c949610430ff27cf08d01d41e44cbac2ff_amd64 as a component of OSSO 1.2 for RHEL 8
  • openshift-secondary-scheduler-operator/secondary-scheduler-operator-rhel8@sha256:864b263c4dfee9c6144a910f59b6155d20fb48f49f0490efb5d14d383ba2bb84_amd64 as a component of OSSO 1.2 for RHEL 8

✅ Remediation

Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 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 (11)