Apache Log4j 2 Vulnerability (CVE-2021-44228)

On this page, we provide the latest update of the potential impact of the open-source Apache “Log4j 2” vulnerability on Google Cloud products and services.  For updates from the Google Cybersecurity Action Team on recommendations for investigating and responding to this Log4j vulnerability please visit this blog post. 

Google Cloud is actively following the security vulnerability in the open-source Apache “Log4j 2" utility (CVE-2021-44228). We are currently assessing the potential impact of the vulnerability for Google Cloud products and services. This is an ongoing event and we will continue to provide updates through our customer communications channels. This advisory page will be updated to include relevant information on our assessment. 

Background: The Apache Log4j utility is a commonly used component for logging requests. On December 9, 2021, a vulnerability was reported that could allow a system running Apache Log4j version 2.14.1 or below to be compromised and allow an attacker to execute arbitrary code. 

On December 10, 2021, NIST published a critical Common Vulnerabilities and Exposure alert, CVE-2021-44228. More specifically, Java Naming Directory Interface (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 remote servers when message lookup substitution is enabled.

What should I do to protect myself? 

We strongly encourage customers who manage environments containing Log4j 2 to update to the latest version. 

Additional Google Cloud product and service-specific information:

Actifio: Actifio now believes that there is limited exposure to the Log4j vulnerability and has released a hotfix to address this vulnerability.  Please visit https://now.actifio.com for the full statement and to obtain the hotfix (available to Actifio customers only). 

Apigee: Apigee has conducted a detailed investigation and we believe that the Edge and OPDK products are not vulnerable to the Log4j 2 vulnerability. Visit the Apigee Incident Report for more information. 

AppSheet: The AppSheet core platform runs on non-JVM (non-Java) based runtimes. At this time, we have identified no impact to core AppSheet functionality. Additionally, we have patched one Java-based auxiliary service in our platform. We will continue to monitor for affected services and patch or remediate as required.

If you have any questions or require assistance, please contact AppSheet Support. 

Google Cloud VMWare Engine: We are working with VMWare and tracking VMSA-2021-0028.1. We will deploy fixes as they become available.

Migrate for Compute Engine (M4CE): We have identified a remote code execution (RCE) vulnerability in the java logging library "Log4j 2" used by M4CE v4.11 or below (as detailed in CVE-2021-44228). A fix for M4CE v4.11 (or below) has been provided in a notification sent to customers on December 13, 2021 with subject line Important information about CVE-2021-44228 for M4CE V4.11 or below. 

If you are on M4CE v5.0 or above, no action is needed.

Information on this page last updated 7:30pm EST on December 14, 2021.