RHSA-2024:3467HighCVSS 7.5

Red Hat Security Advisory: Red Hat OpenStack Platform 16.1 (etcd) security update

Published
May 29, 2024
Last Modified
September 16, 2026

🔗 CVE IDs covered (9)

CVE-2023-39319 →CVE-2023-39322 →CVE-2023-39326 →CVE-2023-39318 →CVE-2023-39321 →CVE-2023-45288 →CVE-2024-4436 →CVE-2024-4437 →CVE-2024-4438 →

📋 Description

CVE-2023-39318 — golang: html/template: improper handling of HTML-like comments within script contexts CVE-2023-39319 — golang: html/template: improper handling of special tags within script contexts CVE-2023-39321 — golang: crypto/tls: panic when processing post-handshake message on QUIC connections CVE-2023-39322 — golang: crypto/tls: lack of a limit on buffered post-handshake CVE-2023-39326 — golang: net/http/internal: Denial of Service (DoS) via Resource Consumption via HTTP requests CVE-2023-45288 — golang: net/http, x/net/http2: unlimited number of CONTINUATION frames causes DoS CVE-2024-4436 — etcd: Incomplete fix for CVE-2022-41723 in OpenStack Platform CVE-2024-4437 — etcd: Incomplete fix for CVE-2021-44716 in OpenStack Platform CVE-2024-4438 — etcd: Incomplete fix for CVE-2023-39325/CVE-2023-44487 in OpenStack Platform

🎯 Affected products8

  • Red Hat OpenStack Platform 16.1
  • etcd-0:3.3.23-16.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.1
  • etcd-0:3.3.23-16.el8ost.src as a component of Red Hat OpenStack Platform 16.1
  • etcd-0:3.3.23-16.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.1
  • etcd-debuginfo-0:3.3.23-16.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.1
  • etcd-debuginfo-0:3.3.23-16.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.1
  • etcd-debugsource-0:3.3.23-16.el8ost.ppc64le as a component of Red Hat OpenStack Platform 16.1
  • etcd-debugsource-0:3.3.23-16.el8ost.x86_64 as a component of Red Hat OpenStack Platform 16.1

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Workaround: No mitigation is available for this flaw. Workaround: In some environments where http/2 support is not required, it may be possible to disable this feature to reduce risk.

🔗 References (12)