[<prev] [next>] [day] [month] [year] [list]
Message-ID: <943ce266-8f32-d763-2980-41c3126222d3@apache.org>
Date: Tue, 18 Jan 2022 14:42:35 +0000
From: Ralph Goers <rgoers@...che.org>
To: oss-security@...ts.openwall.com
Subject: CVE-2022-23305: SQL injection in JDBC Appender in Apache Log4j V1
Severity: high
Description:
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.
Mitigation:
Users should upgrade to Log4j 2 or remove usage of the JDBCAppender from their configurations.
Credit:
Daniel Martin of NCC Group
References:
https://logging.apache.org/log4j/2.x/security.html
https://issues.apache.org/jira/browse/LOG4J2-229
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
