log4j-1.2.17-18.0.1.el7.AXS7

Log4j is a tool to help the programmer output log statements to a variety of
output targets.

Security Fix(es):

* log4j: SQL injection in Log4j 1.x when application is configured to use
JDBCAppender (CVE-2022-23305)
* log4j: Unsafe deserialization flaw in Chainsaw log viewer (CVE-2022-23307)
* log4j: Remote code execution in Log4j 1.x when application is configured to
use JMSSink (CVE-2022-23302)

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.

CVE-2022-23302
JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of
untrusted data when the attacker has write access to the Log4j configuration or
if the configuration references an LDAP service the attacker has access to. The
attacker can provide a TopicConnectionFactoryBindingName configuration causing
JMSSink to perform JNDI requests that result in remote code execution in a
similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when
specifically configured to use JMSSink, which is not the default. Apache Log4j
1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it
addresses numerous other issues from the previous versions.
CVE-2022-23305
By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a
configuration parameter where the values to be inserted are converters from
PatternLayout. The message converter, %m, is likely to always be included. This
allows attackers to manipulate the SQL by entering crafted strings into input
fields or headers of an application that are logged allowing unintended SQL
queries to be executed. Note this issue only affects Log4j 1.x when specifically
configured to use the JDBCAppender, which is not the default. Beginning in
version 2.0-beta8, the JDBCAppender was re-introduced with proper support for
parameterized SQL queries and further customization over the columns written to
in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should
upgrade to Log4j 2 as it addresses numerous other issues from the previous
versions.
CVE-2022-23307
CVE-2020-9493 identified a deserialization issue that was present in Apache
Chainsaw. Prior to Chainsaw V2.0 Chainsaw was a component of Apache Log4j 1.2.x
where the same issue exists.