RHSA-2022:0439HighCVSS 8.8

Red Hat Security Advisory: rh-maven36-log4j12 security update

Published
February 3, 2022
Last Modified
August 4, 2026

🔗 CVE IDs covered (3)

CVE-2022-23302 →CVE-2022-23305 →CVE-2022-23307 →

📋 Description

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 products8

  • Red Hat Software Collections for RHEL Workstation(v. 7)
  • Red Hat Software Collections for RHEL(v. 7)
  • rh-maven36-log4j12-0:1.2.17-23.4.el7.noarch as a component of Red Hat Software Collections for RHEL Workstation(v. 7)
  • rh-maven36-log4j12-0:1.2.17-23.4.el7.noarch as a component of Red Hat Software Collections for RHEL(v. 7)
  • rh-maven36-log4j12-0:1.2.17-23.4.el7.src as a component of Red Hat Software Collections for RHEL Workstation(v. 7)
  • rh-maven36-log4j12-0:1.2.17-23.4.el7.src as a component of Red Hat Software Collections for RHEL(v. 7)
  • rh-maven36-log4j12-javadoc-0:1.2.17-23.4.el7.noarch as a component of Red Hat Software Collections for RHEL Workstation(v. 7)
  • rh-maven36-log4j12-javadoc-0:1.2.17-23.4.el7.noarch as a component of Red Hat Software Collections for RHEL(v. 7)

✅ 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: 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 (6)