RHSA-2022:0435HighCVSS 8.8

Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.4 security update

Published
February 3, 2022
Last Modified
September 22, 2026

🔗 CVE IDs covered (4)

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

📋 Description

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 products200

  • Red Hat JBoss Enterprise Application Platform
  • @babel.code-frame-7.0.0 as a component of Red Hat JBoss Enterprise Application Platform
  • @babel.core-7.4.5 as a component of Red Hat JBoss Enterprise Application Platform
  • @babel.generator-7.4.4 as a component of Red Hat JBoss Enterprise Application Platform
  • @babel.helper-function-name-7.1.0 as a component of Red Hat JBoss Enterprise Application Platform
  • @babel.helper-get-function-arity-7.0.0 as a component of Red Hat JBoss Enterprise Application Platform
  • @babel.helper-split-export-declaration-7.4.4 as a component of Red Hat JBoss Enterprise Application Platform
  • @babel.helpers-7.4.4 as a component of Red Hat JBoss Enterprise Application Platform
  • @babel.highlight-7.0.0 as a component of Red Hat JBoss Enterprise Application Platform
  • @babel.parser-7.4.5 as a component of Red Hat JBoss Enterprise Application Platform
  • @babel.template-7.4.4 as a component of Red Hat JBoss Enterprise Application Platform
  • @babel.traverse-7.4.5 as a component of Red Hat JBoss Enterprise Application Platform
  • @babel.types-7.4.4 as a component of Red Hat JBoss Enterprise Application Platform
  • @mrmlnc.readdir-enhanced-2.2.1 as a component of Red Hat JBoss Enterprise Application Platform
  • @nodelib.fs.stat-1.1.3 as a component of Red Hat JBoss Enterprise Application Platform
  • @types.c3-0.6.0 as a component of Red Hat JBoss Enterprise Application Platform
  • @types.d3-4.13.0 as a component of Red Hat JBoss Enterprise Application Platform
  • @types.d3-array-1.2.1 as a component of Red Hat JBoss Enterprise Application Platform
  • @types.d3-axis-1.0.10 as a component of Red Hat JBoss Enterprise Application Platform
  • @types.d3-brush-1.0.8 as a component of Red Hat JBoss Enterprise Application Platform
  • @types.d3-chord-1.0.7 as a component of Red Hat JBoss Enterprise Application Platform
  • @types.d3-collection-1.0.7 as a component of Red Hat JBoss Enterprise Application Platform
  • @types.d3-color-1.2.1 as a component of Red Hat JBoss Enterprise Application Platform
  • @types.d3-dispatch-1.0.6 as a component of Red Hat JBoss Enterprise Application Platform
  • @types.d3-drag-1.2.1 as a component of Red Hat JBoss Enterprise Application Platform
  • @types.d3-dsv-1.0.33 as a component of Red Hat JBoss Enterprise Application Platform
  • @types.d3-ease-1.0.7 as a component of Red Hat JBoss Enterprise Application Platform
  • @types.d3-force-1.1.1 as a component of Red Hat JBoss Enterprise Application Platform
  • @types.d3-format-1.3.0 as a component of Red Hat JBoss Enterprise Application Platform
  • @types.d3-geo-1.10.3 as a component of Red Hat JBoss Enterprise Application Platform
  • +170 more not shown

✅ Remediation

Before applying this update, back up your existing Red Hat JBoss Enterprise Application Platform installation and deployed applications. The References section of this erratum contains a download link (you must log in to download the update). 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)