As many webmaster and security administrators are looking for how to mitigate the impact of the LOG4J vulnerability, here is an extract taken from a couple of Government pages. I am not the author; I am replicating them for sake of providing a quick link for those how might need them.
“Apache Log4j2 2.0-beta9 through 2.12.1 and 2.13.0 through 2.15.0 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. From version 2.16.0, this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.” nist.gov
From the USA GovCERT References to Advisories, Solutions, and Tools #log4j here:
Apache Log4j Vulnerability Guidance | CISA
From the Swiss Government’s GovCERT:
hZero-Day Exploit Targeting Popular Java Library Log4j (govcert.ch)