First published: Thu Feb 03 2022(Updated: )
Log4j is a tool to help the programmer output log statements to a variety of output targets.<br>Security Fix(es):<br><li> log4j: SQL injection in Log4j 1.x when application is configured to use JDBCAppender (CVE-2022-23305)</li> <li> log4j: Unsafe deserialization flaw in Chainsaw log viewer (CVE-2022-23307)</li> <li> log4j: Remote code execution in Log4j 1.x when application is configured to use JMSSink (CVE-2022-23302)</li> For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/rh-maven36-log4j12 | <1.2.17-23.4.el7 | 1.2.17-23.4.el7 |
redhat/rh-maven36-log4j12 | <1.2.17-23.4.el7 | 1.2.17-23.4.el7 |
redhat/rh-maven36-log4j12-javadoc | <1.2.17-23.4.el7 | 1.2.17-23.4.el7 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of RHSA-2022:0439 is critical due to significant vulnerabilities in Log4j that can lead to security breaches.
To fix RHSA-2022:0439, you should upgrade to the fixed version 1.2.17-23.4.el7 of Log4j as provided in the advisory.
RHSA-2022:0439 addresses SQL injection vulnerabilities and unsafe deserialization flaws in Log4j.
The affected software includes the rh-maven36-log4j12 and rh-maven36-log4j12-javadoc packages.
RHSA-2022:0439 was released to address security issues in Log4j on April 12, 2022.