|
Vulnerabilities
< Back

CVE-2022-23302

Updated on 18 Jan 2022

Severity

8.8 High severity

Details

CVSS score
8.8
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE ID
Links
NISTCIRCLRHELUbuntu

Overview

About vulnerability

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.

Details

Affected product:
Apache Commons , Apache Hadoop , Apache Hive , Apache Kafka , Apache Spark , CentOS 6 ELS , CentOS 7 ELS , CentOS 8.4 ELS , CentOS 8.5 ELS , CloudLinux 6 ELS , Eclipse Jetty , Hibernate , Logback , Oracle Linux 6 ELS , Plexus , Reload4j , Spring , accumulo , activeio-core , activemq , agepredictor , ant , apache-log4j-extras , avro , bookkeeper-common-allocator , castor , cocoon , core , cxf , dropwizard-metrics-hadoop-metrics2-reporter , elasticsearch , flume-ng-core , geronimo-xbean , gradle , hbase , incubator-retired-slider , jgit , karaf , logging-flume , lucene , maven , org.ops4j.pax.logging , sisu , slf4j , slider-core , tika , zkclient , zookeeper
Affected packages:
org.apache.karaf.admin.core @ 2.3.1 (+2062 more)
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.

Fixes