GitHub Advisoryadvisory · Maven

GHSA-fp5r-v3w9-4333 JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data

HIGH Published 2021-12-14 Modified 2023-10-26 Official page ↗
Aliases
CVE-2021-4104
Ecosystem
Maven
Packages
log4j:log4j, org.zenframework.z8.dependencies.commons:log4j-1.2.17
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Weaknesses
CWE-502
Reviewed
2021-12-14

Affected packages

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

Description

JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, 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-2021-4104 JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. vulnerability

Weakness · CWE (1)

  • CWE-502 Deserialization of Untrusted Data weakness

References