SQL injection in JDBC Appender in Apache Log4j V1
CVE-2022-23305

9.8CRITICAL

Key Information:

Vendor: Apache
Status: Apache Log4j 1.x
Vendor: CVE Published:; 18 January 2022

Badges

👾 Exploit Exists🟡 Public PoC

Summary

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.

Affected Version(s)

Apache Log4j 1.x 1.2.1

Apache Log4j 1.x < 2.0-alpha1

Exploit Proof of Concept (PoC)

PoC code is written by security researchers to demonstrate the vulnerability can be exploited. PoC code is also a key component for weaponization which could lead to ransomware.

log4shell-finder
Created by HynekPetrak

CVE-2022-RCE
Created by AlphabugX