Red Hat Security Advisory: Custom Metric Autoscaler operator for Red Hat OpenShift security update
🔗 CVE IDs covered (2)
📋 Description
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 products6
- OpenShift Custom Metrics Autoscaler 2
- custom-metrics-autoscaler/custom-metrics-autoscaler-adapter-rhel8@sha256:f3c6056ddc7be68ba0eac90df388e63de70da69d4b4c49a85bad7a4e1ecbeec6_amd64 as a component of OpenShift Custom Metrics Autoscaler 2
- custom-metrics-autoscaler/custom-metrics-autoscaler-admission-webhooks-rhel8@sha256:5fa428c0cfb55c296ec601117ac124a7648c89f10bf6a031691cc08b15bcae4f_amd64 as a component of OpenShift Custom Metrics Autoscaler 2
- custom-metrics-autoscaler/custom-metrics-autoscaler-operator-bundle@sha256:f66bacfad9cab2c65003cc86331a42fe68336a73feaf802365a3badd4cf5f1b5_amd64 as a component of OpenShift Custom Metrics Autoscaler 2
- custom-metrics-autoscaler/custom-metrics-autoscaler-rhel8-operator@sha256:921c402950001225c8dff5bb14b9307eb69f7a7a6bcdecb852c94a0e8e5c255c_amd64 as a component of OpenShift Custom Metrics Autoscaler 2
- custom-metrics-autoscaler/custom-metrics-autoscaler-rhel8@sha256:49bdd152e73c3339c51fce94820a8cbe00bab54e53a02654bc920daa5592bcc0_amd64 as a component of OpenShift Custom Metrics Autoscaler 2
✅ 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 (6)
- selfhttps://access.redhat.com/errata/RHSA-2023:6144
- externalhttps://access.redhat.com/security/updates/classification/#important
- externalhttps://access.redhat.com/security/vulnerabilities/RHSB-2023-003
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2242803
- externalhttps://issues.redhat.com/browse/OCPBUGS-22361
- selfhttps://security.access.redhat.com/data/csaf/v2/advisories/2023/rhsa-2023_6144.json