Red Hat Bug Fix Advisory: Red Hat Integration - Service Registry 2.4.4 SP1 OpenShift images
🔗 CVE IDs covered (1)
📋 Description
CVE-2023-44487 — HTTP/2: Multiple HTTP/2 enabled web servers are vulnerable to a DDoS attack (Rapid Reset Attack)
🎯 Affected products5
- Middleware Containers for OpenShift
- integration/service-registry-kafkasql-rhel8@sha256:f928407fd0731cdee2705bb1a900dfbbe4ac3be66b3389ce3ebeea1077eaf168_amd64 as a component of Middleware Containers for OpenShift
- integration/service-registry-rhel8-operator-metadata@sha256:d1072a41462dc4d8635781987395dcb81f1c93461d13c749bf86ef725d2deda4_amd64 as a component of Middleware Containers for OpenShift
- integration/service-registry-rhel8-operator@sha256:f985db86e9edfa151b0cc60955169bda69a67f71e49b7c021b3569a1d53b76f5_amd64 as a component of Middleware Containers for OpenShift
- integration/service-registry-sql-rhel8@sha256:6755c8dde41180c6b18493d3dc80bd8628667b8e9c0c92ac150fc2583fa82d14_amd64 as a component of Middleware Containers for OpenShift
✅ 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.