VYPR
← All advisories
High severityNVD Advisory· Published Jan 18, 2022· Updated Jul 7, 2025

Deserialization of untrusted data in JMSSink in Apache Log4j 1.x

CVE-2022-23302

Description

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.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

JMSSink in Log4j 1.x deserializes untrusted data via JNDI, leading to RCE when attacker controls configuration or LDAP service.

Vulnerability

JMSSink in all versions of Log4j 1.x (1.0 through 1.2.17) is vulnerable to deserialization of untrusted data when an attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker controls. This component is not enabled by default. [1][4]

Exploitation

An attacker with write access to the Log4j configuration can set the TopicConnectionFactoryBindingName property to a malicious JNDI URI. Alternatively, if the configuration already references an attacker-controlled LDAP service, the attacker can manipulate the data in that LDAP store. When JMSSink processes the configuration, it performs a JNDI lookup that deserializes untrusted data, leading to remote code execution. This attack vector is similar to CVE-2021-4104. [1][4]

Impact

Successful exploitation allows an attacker to execute arbitrary code in the context of the application using Log4j, resulting in full compromise of confidentiality, integrity, and availability. [1][4]

Mitigation

Apache Log4j 1.x reached end of life in August 2015 and no patches will be released. Users must upgrade to Log4j 2, which addresses this and other security issues. As a workaround, remove or disable any JMSSink configuration in Log4j 1.x deployments. [2][3][4]

References
  1. NVD - CVE-2022-23302
  2. GitHub - apache/logging-log4j1: Apache log4j1
  3. Apache log4j 1.2 -
  4. security - CVE-2022-23302: Deserialization of untrusted data in JMSSink in Apache Log4j 1.x

AI Insight generated on May 21, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected packages

Versions sourced from the GitHub Security Advisory.

PackageAffected versionsPatched versions
log4j:log4jMaven
<= 1.2.17—
org.zenframework.z8.dependencies.commons:log4j-1.2.17Maven
<= 2.0—

Affected products

180

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

11

News mentions

0

No linked articles in our index yet.