GCP-2021-026

<strong>Published:</strong><br/><table class="fixed"> <thead> <tr> <th width="70%">Description</th> <th>Severity</th> <th>Notes</th> </tr> </thead> <tbody> <tr> <td> <p>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.</p> <p>On December 10, 2021, NIST published a critical Common Vulnerabilities and Exposure alert, <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-44228">CVE-2021-44228</a>. More specifically, Java Naming Directory Interface (JNDI) features used in configuration, log messages, and parameters don't 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.</p> <h4 data-text="What should I do?" id="what-should-i-do_17" tabindex="-1">What should I do?</h4> <ul> <li><strong>M4CE v4.x:</strong> The Migrate for Compute Engine (M4CE) Team has provided a new version on 13 December, 2021. Project managers are required to replace the existing deployment with the new version including in-cloud M4CE Manager and M4CE "on premises" backend. See the <a href="https://docs.cloud.google.com/migrate/compute-engine/docs/4.11/how-to">How to Guide</a> for details on version 4.11 deploy details.</li> <li><strong>M2VMs v5.x:</strong> M2VMs v5.0 and above has been fixed and no action is required.</li> </ul> </td> <td> Critical </td> <td> <ul> <li><a href="https://nvd.nist.gov/vuln/detail/CVE-2021-44228" target="mitre">CVE-2021-44228</a></li> </ul> </td> </tr> </tbody> </table>