Deserialization of untrusted data

2022-01-1816:15:00

PRIOn knowledge base

www.prio-n.com

9.1 High

AI Score

Confidence

High

0.127 Low

EPSS

Percentile

95.5%

JSON

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.

CPENameOperatorVersion
log4jge1.0.1
log4jle1.2.17
advanced_supply_chain_planningeq12.2
advanced_supply_chain_planningeq12.1
business_intelligenceeq12.2.1.3.0
business_intelligenceeq12.2.1.4.0
business_intelligenceeq5.9.0.0.0
business_process_management_suiteeq12.2.1.3.0
business_process_management_suiteeq12.2.1.4.0
communications_eagle_ftp_table_base_retrievaleq4.5

Name	Operator	Version
log4j	ge	1.0.1
log4j	le	1.2.17
advanced_supply_chain_planning	eq	12.2
advanced_supply_chain_planning	eq	12.1
business_intelligence	eq	12.2.1.3.0
business_intelligence	eq	12.2.1.4.0
business_intelligence	eq	5.9.0.0.0
business_process_management_suite	eq	12.2.1.3.0
business_process_management_suite	eq	12.2.1.4.0
communications_eagle_ftp_table_base_retrieval	eq	4.5