Description
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.
Remediation
References
http://www.openwall.com/lists/oss-security/2022/01/18/3
https://lists.apache.org/thread/bsr3l5qz4g0myrjhy9h67bcxodpkwj4w
https://logging.apache.org/log4j/1.2/index.html
https://security.netapp.com/advisory/ntap-20220217-0006/
https://www.oracle.com/security-alerts/cpuapr2022.html
https://www.oracle.com/security-alerts/cpujul2022.html
Related Vulnerabilities
CVE-2021-27405 Vulnerability in npm package @progfay/scrapbox-parser
CVE-2021-21364 Vulnerability in maven package io.swagger:swagger-codegen
CVE-2019-10337 Vulnerability in maven package org.jenkins-ci.plugins:token-macro
CVE-2022-4245 Vulnerability in maven package org.codehaus.plexus:plexus-utils
CVE-2019-10390 Vulnerability in maven package com.splunk.splunkins:splunk-devops