REDHAT-BUG-2041959

First published: Tue Jan 18 2022(Updated: )

By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converted 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. References: <a href="https://www.openwall.com/lists/oss-security/2022/01/18/4">https://www.openwall.com/lists/oss-security/2022/01/18/4</a>

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

• agent/type
• agent/first-publish-date
• agent/severity
• agent/description
• agent/event
• agent/references
• agent/last-modified-date
• agent/trending
• agent/source
• agent/guess-ai
• agent/software-canonical-lookup
• agent/softwarecombine
• agent/tags
• collector/redhat-bugzilla
• source/Red Hat
• alias/CVE-2022-23305
• vendor/apache
• canonical/apache log4j