RHEA-2024:0555HighCVSS 7.5

Red Hat Enhancement Advisory: Release of AWS Load Balancer Operator 1.1.z on OperatorHub

Published
January 30, 2024
Last Modified
August 18, 2026

🔗 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 products4

  • AWS-LB-OPTR 1.1 for RHEL 8
  • albo/aws-load-balancer-controller-rhel8@sha256:66765344a934482abe5f14cf6906e8aeca7abdc23cea7ba4cbbd84906c6f754f_amd64 as a component of AWS-LB-OPTR 1.1 for RHEL 8
  • albo/aws-load-balancer-operator-bundle@sha256:01f2ca529d2486f113bcefc9fedce6a6fd07bcb48aaf534394b5b04c353f8853_amd64 as a component of AWS-LB-OPTR 1.1 for RHEL 8
  • albo/aws-load-balancer-rhel8-operator@sha256:e3780dc698436ec7fd624ab0060c505743eca4d9b900aa9794b8888a2660f287_amd64 as a component of AWS-LB-OPTR 1.1 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: 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 (2)