RHSA-2023:6171CriticalCVSS 9.8

Red Hat Security Advisory: Red Hat Product OCP Tools 4.11 Openshift Jenkins security update

Published
October 30, 2023
Last Modified
August 24, 2026

🔗 CVE IDs covered (9)

📋 Description

CVE-2022-1471 — SnakeYaml: Constructor Deserialization Remote Code Execution CVE-2022-29599 — maven-shared-utils: Command injection via Commandline class CVE-2022-42889 — apache-commons-text: variable interpolation RCE CVE-2023-24422 — jenkins-2-plugins/script-security: Sandbox bypass vulnerability in Script Security Plugin CVE-2023-25761 — jenkins-2-plugins/JUnit: Stored XSS vulnerability in JUnit Plugin CVE-2023-25762 — jenkins-2-plugins/pipeline-build-step: Stored XSS vulnerability in Pipeline: Build Step Plugin CVE-2023-27903 — Jenkins: Temporary file parameter created with insecure permissions CVE-2023-27904 — Jenkins: Information disclosure through error stack traces related to agents CVE-2023-39325 — golang: net/http, x/net/http2: rapid stream resets can cause excessive work (CVE-2023-44487)

🎯 Affected products5

  • OpenShift Developer Tools and Services for OCP 4.11 for RHEL 8
  • jenkins-0:2.414.3.1698298955-3.el8.noarch as a component of OpenShift Developer Tools and Services for OCP 4.11 for RHEL 8
  • jenkins-0:2.414.3.1698298955-3.el8.src as a component of OpenShift Developer Tools and Services for OCP 4.11 for RHEL 8
  • jenkins-2-plugins-0:4.11.1698299029-1.el8.noarch as a component of OpenShift Developer Tools and Services for OCP 4.11 for RHEL 8
  • jenkins-2-plugins-0:4.11.1698299029-1.el8.src as a component of OpenShift Developer Tools and Services for OCP 4.11 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: This flaw may be avoided by ensuring that any external inputs used with the Commons-Text lookup methods are sanitized properly. Untrusted input should always be thoroughly sanitized before using in any potentially risky situations. 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.

🔗 References (3)