CVE-2022-23302: Log4j Deserialization Of Untrusted Data Vulnerability
HIGHCVE-2022-23302 is a HIGH (CVSS 8.8) deserialization of untrusted data vulnerability (CWE-502: Deserialization of Untrusted Data) affecting Log4j libraries in the Maven ecosystem. The issue involves deserialization of untrusted data in log4j 1.x. Remediation is available in the latest vendor maintenance releases.
CVE-2022-23302 at a Glance
Security Impact
CVSS: 8.8
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).
How to Fix CVE-2022-23302
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-23302, 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-502: Deserialization of Untrusted Data, where the product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. 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-23302 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-23302?
Which Log4j versions are affected?
What version fixes CVE-2022-23302?
Is log4j affected?
Is log4j-1.2.17 affected?
What is the CVSS score of CVE-2022-23302?
What CWE is associated with CVE-2022-23302?
How can I check Maven dependencies for CVE-2022-23302?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-w9p3-5cr8-m3jj",
"modified" : "2025-07-09T14:59:08Z",
"published" : "2022-01-21T23:27:14Z",
"aliases" : [ "CVE-2022-23302" ],
"summary" : "Deserialization of Untrusted Data in Log4j 1.x",
"details" : "JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, 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.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/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-23302"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/apache/logging-log4j1"
}, {
"type" : "WEB",
"url" : "https://lists.apache.org/thread/bsr3l5qz4g0myrjhy9h67bcxodpkwj4w"
}, {
"type" : "WEB",
"url" : "https://logging.apache.org/log4j/1.2/index.html"
}, {
"type" : "WEB",
"url" : "https://security.netapp.com/advisory/ntap-20220217-0006"
}, {
"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" : "https://www.vicarius.io/vsociety/posts/cve-2022-23302-detect-log4j-1217-vulnerability"
}, {
"type" : "WEB",
"url" : "https://www.vicarius.io/vsociety/posts/cve-2022-23302-mitigate-log4j-1217-vulnerability"
}, {
"type" : "WEB",
"url" : "http://www.openwall.com/lists/oss-security/2022/01/18/3"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-502" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2022-01-19T22:31:40Z",
"nvd_published_at" : "2022-01-18T16:15:00Z"
}
}