CVE-2022-23305: Log4j SQL Injection Vulnerability
CRITICALCVE-2022-23305 is a CRITICAL (CVSS 9.8) sql injection vulnerability (CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')) affecting Log4j libraries in the Maven ecosystem. The issue involves sql injection in log4j 1.2.x. Remediation is available in the latest vendor maintenance releases.
CVE-2022-23305 at a Glance
Security Impact
CVSS: 9.8
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
How to Fix CVE-2022-23305
To remediate this vulnerability, upgrade all affected Log4j dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>Latest secure release</version>
</dependency><dependency>
<groupId>org.zenframework.z8.dependencies.commons</groupId>
<artifactId>log4j-1.2.17</artifactId>
<version>Latest secure release</version>
</dependency>Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=log4jHow to Check if You Are Affected
To determine whether your Java application is affected by CVE-2022-23305, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=log4jAnalyze the terminal output to locate any version of Log4j in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.
Note: The mvn dependency:tree -Dincludes=log4j command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'), where the product constructs all or part of an sql command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended sql command when it is sent to a downstream component. without sufficient removal or quoting of sql syntax in user-controllable inputs, the generated sql query can cause those inputs to be interpreted as sql instead of ordinary user data. In Log4j, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2022-23305 Affected Log4j Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
log4j:log4j
|
Maven |
≤ 1.2.17
|
|
|
org.zenframework.z8.dependencies.commons:log4j-1.2.17
|
Maven |
≤ 2.0
|
|
References
Frequently Asked Questions
What is CVE-2022-23305?
Which Log4j versions are affected?
What version fixes CVE-2022-23305?
Is log4j affected?
Is log4j-1.2.17 affected?
What is the CVSS score of CVE-2022-23305?
What CWE is associated with CVE-2022-23305?
How can I check Maven dependencies for CVE-2022-23305?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-65fg-84f6-3jq3",
"modified" : "2026-06-08T23:39:52Z",
"published" : "2022-01-21T23:26:47Z",
"aliases" : [ "CVE-2022-23305" ],
"summary" : "SQL Injection in Log4j 1.2.x",
"details" : "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.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "log4j:log4j"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "1.2.17"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "org.zenframework.z8.dependencies.commons:log4j-1.2.17"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "2.0"
} ]
} ]
} ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-23305"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/apache/logging-log4j1"
}, {
"type" : "WEB",
"url" : "https://lists.apache.org/thread/pt6lh3pbsvxqlwlp4c5l798dv2hkc85y"
}, {
"type" : "WEB",
"url" : "https://logging.apache.org/log4j/1.2/index.html"
}, {
"type" : "WEB",
"url" : "https://security.netapp.com/advisory/ntap-20220217-0007"
}, {
"type" : "WEB",
"url" : "https://www.oracle.com/security-alerts/cpuapr2022.html"
}, {
"type" : "WEB",
"url" : "https://www.oracle.com/security-alerts/cpujul2022.html"
}, {
"type" : "WEB",
"url" : "http://www.openwall.com/lists/oss-security/2022/01/18/4"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-89" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2022-01-19T22:31:49Z",
"nvd_published_at" : "2022-01-18T16:15:00Z"
}
}