CVE-2021-44228 (log4j) Apache vulnerability - How does this affect security in ServiceNow?

Kelly Logan
Kilo Sage

‎12-10-2021 07:19 AM

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 by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class). Java 8u121 (see 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".

https://nvd.nist.gov/vuln/detail/CVE-2021-44228

Exploit code has been released for a serious code-execution vulnerability in Log4j, an open-source logging utility that's used in countless apps, including those used by large enterprise organizations, several websites reported on last Thursday.

https://arstechnica.com/information-technology/2021/12/minecraft-and-other-apps-face-serious-threat-from-new-code-execution-bug/

Labels:
  • 20,821 Views
27 REPLIES 27

Dave Mau
ServiceNow Employee
ServiceNow Employee

‎12-11-2021 02:26 PM

KB Has been updated with additional information.

0 Helpfuls

robertbeck
Kilo Contributor
In response to Dave Mau

‎12-11-2021 04:01 PM

Knowledge record not found...

0 Helpfuls

Dan T_
Tera Guru
In response to robertbeck

‎12-11-2021 04:05 PM

Log in to HI Support before trying the link

0 Helpfuls

vilmarsteur
Tera Contributor

‎12-12-2021 01:20 AM

@Dave Mau  Is there any outlook on when a emergency security patch will be distributed to go from 2.14.1 to 2.15 on the OOT distribution of the Mid Server application? 

Frank Tate
Giga Guru
Giga Guru
In response to vilmarsteur

‎12-13-2021 10:28 AM

You can implement an emergency fix right now. Find any/all files named log4j-core-2*.jar and remove the file org/apache/logging/log4j/core/lookup/JndiLookup.class from them and restart the MID server. On Linux, this can be accomplished with:

find / -name "log4j-core-*.jar" -exec zip -q -d {} org/apache/logging/log4j/core/lookup/JndiLookup.class \;
 
Frank
0 Helpfuls