Critical

SQL Injection in Log4j 1.2.x

  • Disclosed: 21.01.2022
  • Updated: 11.10.2026 12:22

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 software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Java / Kotlin (Maven) log4j:log4j <= 1.2.17 no fix
Java / Kotlin (Maven) org.zenframework.z8.dependencies.commons:log4j-1.2.17 <= 2.0 no fix

References

CVSS score 9.8/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE)
CWE-89
Platform
Java / Kotlin (Maven)
Package
log4j:log4j, org.zenframework.z8.dependencies.commons:log4j-1.2.17
Disclosed
21.01.2022
Updated
11.10.2026 12:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-65fg-84f6-3jq3 - CC BY 4.0

Vulnerability history: log4j:log4j

All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.

Total entries
6
First → latest
01.2020 03.2023
Without a fix
5
Exploited in attacks
0

Severity breakdown

  • Critical 3
  • High 3

Disclosures per year

  1. 2020: 1
  2. 2021: 1
  3. 2022: 3
  4. 2023: 1
  5. 2024: 0
  6. 2025: 0
  7. 2026: 0
  1. High · 7.5 CVE-2023-26464 >= 1.0.4, < 2.0 2.0
  2. High · 8.8 CVE-2022-23302 <= 1.2.17 no fix
  3. SQL Injection in Log4j 1.2.x this entry
    Critical · 9.8 CVE-2022-23305 <= 1.2.17 no fix
  4. Critical · 9.8 CVE-2022-23307 <= 1.2.17 no fix
  5. High · 7.5 CVE-2021-4104 >= 1.2.0, <= 1.2.17 no fix
  6. Critical · 9.8 CVE-2019-17571 >= 1.2, <= 1.2.17 no fix

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.