Log4j is an open-source, Java-based logging utility widely used by enterprise applications and cloud services.
Apache Log4j from versions 2.14.1 and below 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.
In the updated version, log4j 2.15.0, this behavior has been disabled by default.
In previous releases greater than versin 2.10, this behavior can be mitigated by setting system property “log4j2.formatMsgNoLookups” to “true” or by removing the JndiLookup class from the classpath.
Java 8u121 https://www.oracle.com/java/technologies/javase/8u121-relnotes.html protects against remote code execution by defaulting “com.sun.jndi.rmi.object.trustURLCodebase” and “com.sun.jndi.cosnaming.object.trustURLCodebase” to “false.”
Click here for the Apache Log4j 2.15.0 advisory and upgrade to Log4j 2.15.0 or apply the recommended mitigations.

