RHSA-2023:5805HighCVSS 7.5

Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.4 Product Security and Bug Fix Update

Published
October 17, 2023
Last Modified
September 30, 2026

🔗 CVE IDs covered (3)

CVE-2023-44487 →CVE-2023-29409 →CVE-2023-39325 →

📋 Description

CVE-2023-29409 — golang: crypto/tls: slow verification of certificate chains containing large RSA keys 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 products14

  • Red Hat Ansible Automation Platform 2.4 for RHEL 8
  • Red Hat Ansible Automation Platform 2.4 for RHEL 9
  • receptor-0:1.4.2-1.el8ap.aarch64 as a component of Red Hat Ansible Automation Platform 2.4 for RHEL 8
  • receptor-0:1.4.2-1.el8ap.ppc64le as a component of Red Hat Ansible Automation Platform 2.4 for RHEL 8
  • receptor-0:1.4.2-1.el8ap.s390x as a component of Red Hat Ansible Automation Platform 2.4 for RHEL 8
  • receptor-0:1.4.2-1.el8ap.src as a component of Red Hat Ansible Automation Platform 2.4 for RHEL 8
  • receptor-0:1.4.2-1.el8ap.x86_64 as a component of Red Hat Ansible Automation Platform 2.4 for RHEL 8
  • receptor-0:1.4.2-1.el9ap.aarch64 as a component of Red Hat Ansible Automation Platform 2.4 for RHEL 9
  • receptor-0:1.4.2-1.el9ap.ppc64le as a component of Red Hat Ansible Automation Platform 2.4 for RHEL 9
  • receptor-0:1.4.2-1.el9ap.s390x as a component of Red Hat Ansible Automation Platform 2.4 for RHEL 9
  • receptor-0:1.4.2-1.el9ap.src as a component of Red Hat Ansible Automation Platform 2.4 for RHEL 9
  • receptor-0:1.4.2-1.el9ap.x86_64 as a component of Red Hat Ansible Automation Platform 2.4 for RHEL 9
  • receptorctl-0:1.4.2-1.el8ap.noarch as a component of Red Hat Ansible Automation Platform 2.4 for RHEL 8
  • receptorctl-0:1.4.2-1.el9ap.noarch as a component of Red Hat Ansible Automation Platform 2.4 for RHEL 9

✅ Remediation

Red Hat Ansible Automation Platform 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 (7)