RHSA-2023:4657MediumCVSS 9.8

Red Hat Security Advisory: Secondary Scheduler Operator for Red Hat OpenShift 1.1.2 security update

Published
August 23, 2023
Last Modified
September 17, 2026

🔗 CVE IDs covered (7)

📋 Description

CVE-2023-24532 — golang: crypto/internal/nistec: specific unreduced P-256 scalars produce incorrect results CVE-2023-24534 — golang: net/http, net/textproto: denial of service from excessive memory allocation CVE-2023-24536 — golang: net/http, net/textproto, mime/multipart: denial of service from excessive resource consumption CVE-2023-24537 — golang: go/parser: Infinite loop in parsing CVE-2023-24538 — golang: html/template: backticks not treated as string delimiters CVE-2023-24539 — golang: html/template: improper sanitization of CSS values CVE-2023-29400 — golang: html/template: improper handling of empty HTML attributes

🎯 Affected products3

  • OSSO 1.1 for RHEL 8
  • openshift-secondary-scheduler-operator/secondary-scheduler-operator-bundle@sha256:daea4461ca6a1903f2e2a1470df8fdfe413106e84e0b36789e0fb0e2bbdba333_amd64 as a component of OSSO 1.1 for RHEL 8
  • openshift-secondary-scheduler-operator/secondary-scheduler-operator-rhel8@sha256:5804495067018a355d02f88d2324a43567f0ca2869d02dedbf47973ed6ffeeb3_amd64 as a component of OSSO 1.1 for RHEL 8

✅ 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: Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Workaround: To mitigate this issue, upgrade Go to version 1.19.8, 1.20.3, or later, where the vulnerability has been addressed. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

🔗 References (11)