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.
Workaround:
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
| Link | Tags |
|---|---|
| https://lists.apache.org/thread/bsr3l5qz4g0myrjhy9h67bcxodpkwj4w | vendor advisory mailing list mitigation |
| https://logging.apache.org/log4j/1.2/index.html | vendor advisory |
| http://www.openwall.com/lists/oss-security/2022/01/18/3 | third party advisory mailing list |
| https://www.oracle.com/security-alerts/cpuapr2022.html | third party advisory patch |
| https://security.netapp.com/advisory/ntap-20220217-0006/ | third party advisory |
| https://www.oracle.com/security-alerts/cpujul2022.html | third party advisory patch |