NetSight
high7.5

CVE-2021-4104

JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data

Impact

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.

Affected packages

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

Affected products

VendorProductAffected versions
ApacheLog4j
Version 1.2
FedoraprojectFedora
Version 35
RedhatCodeready Studio
Version 12.0
RedhatIntegration Camel K
All versions
RedhatIntegration Camel Quarkus
All versions
RedhatJboss A-Mq
Versions 6.0.0, 7
RedhatJboss A-Mq Streaming
All versions
RedhatJboss Data Grid
Version 7.0.0
RedhatJboss Data Virtualization
Version 6.0.0
RedhatJboss Enterprise Application Platform
Versions 6.0.0, 7.0
RedhatJboss Fuse
Versions 6.0.0, 7.0.0
RedhatJboss Fuse Service Works
Version 6.0

Weakness classification

References