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

Kelly Logan
Kilo Sage

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/

27 REPLIES 27

Knowledge record not found

Dan T_
Tera Guru

The security advisories page is a handy one to keep bookmarked also - you must be a ServiceNow customer and an HI Support user to access them.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0870307

 

 

 

This page does not seem available

PeterG
Kilo Contributor

Do you know if SNow is vulnerable to Java Virtual Machine or Apache Log4J?

Someone posted a KB article but I cant logon to Hi portal at this time.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0870307

ServiceNow Posture:

ServiceNow has become aware of a 0-day exploit in the popular Java logging library, “log4j.”  

After a thorough investigation, ServiceNow has confirmed that instances of the Now Platform are running a version of Java that, by default, implements settings to prevent this vulnerability.

More clearly, these settings are set as follows:

  • com.sun.jndi.ldap.object.trustURLCodebase=false
  • com.sun.jndi.rmi.object.trustURLCodebase=false

Additionally, MID Servers have log4j turned off for third-party libraries. Moreover, the Java versions that are shipped with the MID Servers are not vulnerable, and have the same settings as listed above. 

We will continue to monitor and perform further testing as needed.