GitHub Advisoryadvisory · Maven

GHSA-65fg-84f6-3jq3 SQL Injection in Log4j 1.2.x

CRITICAL Published 2022-01-21 Modified 2026-06-08 Official page ↗
Aliases
CVE-2022-23305
Ecosystem
Maven
Packages
log4j:log4j, org.zenframework.z8.dependencies.commons:log4j-1.2.17
Severity
Critical
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weaknesses
CWE-89
Reviewed
2022-01-19

Affected packages

• Maven log4j:log4j: <= 1.2.17 (no fix yet) • Maven org.zenframework.z8.dependencies.commons:log4j-1.2.17: <= 2.0 (no fix yet)

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.

Related

Alias · CVE (1)

  • CVE-2022-23305 By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are… vulnerability

Weakness · CWE (1)

  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command weakness

References