CVE-2021-44228-45105 - log4j vulnerabilities and Dollar Universe

Products

• CA Automic Dollar Universe

Issue/Introduction

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45105

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 &#8220;true&#8221; 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".

Environment

Only Java Components could be affected ( UVMS, UVC, DUX, Manager for Java, Reporter).

Cause

Bug in log4j 2.x

Resolution

Broadcom Engineering has confirmed that Dollar Universe Java components are not vulnerable as they use log4j version 1.2.15 and are NOT using any JMS appender.

Log4j Versions Affected: Apache Log4j2 versions 2.0-alpha1 through 2.16.0 

Should you have any further questions or concerns, please open a case with Support.

Additional Information

Upgrade to Dollar Universe v7.0.x or 6.10.101 or superior versions the Java Components.

On this newer version, it's been included a new version of log4j2 that has this vulnerability fixed.