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.
History

Mon, 26 Aug 2024 18:45:00 +0000

Type Values Removed Values Added
First Time appeared Redhat jboss Enterprise Application Platform Eus
CPEs cpe:/a:redhat:jboss_enterprise_application_platform_eus:7.1::el7
Vendors & Products Redhat jboss Enterprise Application Platform Eus

cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published: 2022-01-18T15:25:20

Updated: 2024-08-03T03:36:20.336Z

Reserved: 2022-01-16T00:00:00

Link: CVE-2022-23302

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Analyzed

Published: 2022-01-18T16:15:08.300

Modified: 2023-02-24T15:30:46.490

Link: CVE-2022-23302

cve-icon Redhat

Severity : Moderate

Publid Date: 2022-01-18T00:00:00Z

Links: CVE-2022-23302 - Bugzilla