GitHub Advisoryadvisory · Maven

GHSA-w9p3-5cr8-m3jj Deserialization of Untrusted Data in Log4j 1.x

HIGH Published 2022-01-21 Modified 2025-07-09 Official page ↗
Aliases
CVE-2022-23302
Ecosystem
Maven
Packages
log4j:log4j, org.zenframework.z8.dependencies.commons:log4j-1.2.17
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weaknesses
CWE-502
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

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.

Related

Alias · CVE (1)

  • CVE-2022-23302 JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j… vulnerability

Weakness · CWE (1)

  • CWE-502 Deserialization of Untrusted Data weakness

References