RHSA-2022:0447HighCVSS 8.8

Red Hat Security Advisory: Red Hat Single Sign-On 7.5.1 security update on RHEL 7

Published
February 7, 2022
Last Modified
August 4, 2026

🔗 CVE IDs covered (5)

CVE-2021-3859 →CVE-2021-4104 →CVE-2022-23302 →CVE-2022-23305 →CVE-2022-23307 →

📋 Description

CVE-2021-3859 — undertow: client side invocation timeout raised when calling over HTTP2 CVE-2021-4104 — log4j: Remote code execution in Log4j 1.x when application is configured to use JMSAppender CVE-2022-23302 — log4j: Remote code execution in Log4j 1.x when application is configured to use JMSSink CVE-2022-23305 — log4j: SQL injection in Log4j 1.x when application is configured to use JDBCAppender CVE-2022-23307 — log4j: Unsafe deserialization flaw in Chainsaw log viewer

🎯 Affected products4

  • Red Hat Single Sign-On 7.5 for RHEL 7 Server
  • rh-sso7-keycloak-0:15.0.4-1.redhat_00003.1.el7sso.noarch as a component of Red Hat Single Sign-On 7.5 for RHEL 7 Server
  • rh-sso7-keycloak-0:15.0.4-1.redhat_00003.1.el7sso.src as a component of Red Hat Single Sign-On 7.5 for RHEL 7 Server
  • rh-sso7-keycloak-server-0:15.0.4-1.redhat_00003.1.el7sso.noarch as a component of Red Hat Single Sign-On 7.5 for RHEL 7 Server

✅ 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: These are the possible mitigations for this flaw for releases version 1.x: - Comment out or remove JMSAppender in the Log4j configuration if it is used - Remove the JMSAppender class from the classpath. For example: ``` zip -q -d log4j-*.jar org/apache/log4j/net/JMSAppender.class ``` - Restrict access for the OS user on the platform running the application to prevent modifying the Log4j configuration by the attacker. Workaround: These are the possible mitigations for this flaw for releases version 1.x: - Comment out or remove JMSSink in the Log4j configuration if it is used - Remove the JMSSink class from the server's jar files. For example: ``` zip -q -d log4j-*.jar org/apache/log4j/net/JMSSink.class ``` - Restrict access for the OS user on the platform running the application to prevent modifying the Log4j configuration by the attacker. Workaround: These are the possible mitigations for this flaw for releases version 1.x: - Comment out or remove JDBCAppender in the Log4j configuration if it is used - Remove the JDBCAppender class from the server's jar files. For example: ``` zip -q -d log4j-*.jar org/apache/log4j/jdbc/JDBCAppender.class ``` Workaround: These are the mitigations available for this flaw for log4j 1.x: - Avoid using Chainsaw to view logs, and instead use some other utility, especially if there is a log view available within the product itself. - Remove the Chainsaw classes from the log4j jar files. For example: ``` zip -q -d log4j-*.jar org/apache/log4j/chainsaw/* ``` (log4j jars may be nested in zip archives within product)

🔗 References (10)