RHSA-2023:7484HighCVSS 7.5

Red Hat Security Advisory: Red Hat Single Sign-On 7.6.6 security update on RHEL 9

Published
November 24, 2023
Last Modified
July 30, 2026

🔗 CVE IDs covered (3)

CVE-2023-0105 →CVE-2023-33201 →CVE-2023-44487 →

📋 Description

CVE-2023-0105 — keycloak: impersonation and lockout possible through incorrect handling of email trust CVE-2023-33201 — bouncycastle: potential blind LDAP injection attack using a self-signed certificate CVE-2023-44487 — HTTP/2: Multiple HTTP/2 enabled web servers are vulnerable to a DDoS attack (Rapid Reset Attack)

🎯 Affected products4

  • Red Hat Single Sign-On 7.6 for RHEL 9
  • rh-sso7-keycloak-0:18.0.11-2.redhat_00001.1.el9sso.noarch as a component of Red Hat Single Sign-On 7.6 for RHEL 9
  • rh-sso7-keycloak-0:18.0.11-2.redhat_00001.1.el9sso.src as a component of Red Hat Single Sign-On 7.6 for RHEL 9
  • rh-sso7-keycloak-server-0:18.0.11-2.redhat_00001.1.el9sso.noarch as a component of Red Hat Single Sign-On 7.6 for RHEL 9

✅ 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: 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 (7)