Apache Log4j2 <=2.14.1 JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints.
An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled
From log4j 2.15.0, this behavior has been disabled by default. In previous releases (>2.10) this behavior can be mitigated by setting system property "log4j2.formatMsgNoLookups" to "true"; or adding the environment variable LOG4J_FORMAT_MSG_NO_LOOKUPS": "true" or by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/
[Update 16 December] A further vulnerability (CVE-2021-45046) was disclosed on December 14th and it was found that the configuration mentioned in this KB to mitigate CVE-2021-44228 in Apache Log4j 2.x < 2.16.0 was incomplete in some scenarios.
Engineering is actively working on a permanent fix on top of 21.3.1 with the upgraded log4j 2.16 version.
DX OI SaaS
To remove the JNDI lookups class
1. Goto Onprem-Itsm-->NIM
2. Shutdown the tomcat, by going to <tomcat>/bin path and execute shutdown script
3 Goto <tomcat>/webapps/ca-nim-sm/WEB-INF/lib
4.Remove the JndiLookup class from the classpath: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class
5. Restart the tomcat, by going to <tomcat>/bin and execute startup script
For more information, see https://logging.apache.org/log4j/2.x/security.html