NetSight
high8.8

CVE-2022-23302

Deserialization of Untrusted Data in Log4j 1.x

Impact

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.

Affected packages

EcosystemPackageAffectedFixed in
mavenlog4j:log4j<= 1.2.17none recorded
mavenorg.zenframework.z8.dependencies.commons:log4j-1.2.17<= 2.0none recorded

Affected products

VendorProductAffected versions
ApacheLog4j
from 1.0.1 through 1.2.17
NetappSnapmanager
All versions
BroadcomBrocade Sannav
All versions
QosReload4j
before 1.2.18.1
OracleAdvanced Supply Chain Planning
Versions 12.1, 12.2
OracleBusiness Intelligence
Versions 5.9.0.0.0, 12.2.1.3.0, 12.2.1.4.0
OracleBusiness Process Management Suite
Versions 12.2.1.3.0, 12.2.1.4.0
OracleCommunications Eagle Ftp Table Base Retrieval
Version 4.5
OracleCommunications Instant Messaging Server
Version 10.0.1.5.0
OracleCommunications Messaging Server
Version 8.1
OracleCommunications Network Integrity
Version 7.3.6
OracleCommunications Offline Mediation Controller
before 12.0.0.4.4
Version 12.0.0.5.0

Weakness classification

References