SQL Injection Affecting ch.qos.reload4j:reload4j package, versions [,1.2.18.2)
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-JAVA-CHQOSRELOAD4J-2434293
- published 18 Jan 2022
- disclosed 18 Jan 2022
- credit Unknown
Introduced: 18 Jan 2022
CVE-2022-23305 Open this link in a new tabHow to fix?
Upgrade ch.qos.reload4j:reload4j to version 1.2.18.2 or higher.
Overview
ch.qos.reload4j:reload4j is an a fork of Apache log4j version 1.2.17 with the goal of fixing pressing security issues.
Affected versions of this package are vulnerable to SQL Injection. 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.
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. 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.