In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 02, 2022 - 16:45 PDT
Scheduled - On this page, we provide the latest update of the potential impact of the recently announced OpenSSL vulnerabilities(https://www.openssl.org/blog/blog/2022/11/01/email-address-overflows/) on Apigee products and services. Investigations are ongoing as this is a developing event. We will continue to assess potential impact as we learn more, and we will update this post with details on any impacted Apigee products and services.
As Apigee components do not explicitly install the OpenSSL package in the base images, Apigee products are not found to be impacted with the OpenSSL vulnerability reported on OpenSSL 3.x.
As of this publication, we have found no evidence of any exploitation activities.
We’ll share more information with customers as it becomes available and update this page with the results of our investigation and any guidance if appropriate.
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 01, 2022 - 09:30 PDT
Scheduled - To minimize the risk of service outage during the Holiday 2022 season, Apigee will enforce a “release moratorium” from October 31, 2022 through January 02, 2023.
This moratorium covers critical components including API Services, Management Services UI, Management Services API, Analytics Services, Developer Services, Apigee Login and Single Sign-On, Apigee Sense and Apigee Monetization
During this period, we will only make emergency changes to the system. In the event we need to make any such change, due to security or other concerns, we will notify you before making them.
Update - Log4j v1.x: We are aware of the recent upgrade to CVE-2021-4104 which affects versions of Log4j 1 which are used on Apigee Edge and OPDK. This CVE requires a specific configuration of Log4j 1 which Apigee Edge does not use and which Apigee OPDK does not ship as a default configuration.
User Supplied Log4j 1 Java Callouts Apigee SaaS (X and Edge): Customers can upload vulnerable configurations of Log4j 1 in their custom resources, but CVE-2021-4104 is mitigated due to Java Security Manager restrictions.
Google Apigee is actively following the security vulnerability in the open-source Apache “Log4j 2" utility (CVE-2021-44228 and CVE-2021-45046). We encourage you to update to the latest version of Log4j 2. We are currently assessing the potential impact of the vulnerability for Apigee products and services. This is an ongoing event and we will continue to provide updates through this page and our customer communications channels.
Background: The Apache Log4j 2 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 2 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.
==== Platform ====
Apigee X: Apigee X does not use Log4j 2.
Apigee Hybrid: Current supported versions of Hybrid do not use Log4j 2. Unsupported versions of Hybrid used Log4j 1.x, but it is not included in any of the currently supported versions. Customers on Hybrid 1.4 or lower are unaffected by this CVE but should still upgrade to a supported version.
Apigee Edge: Apigee Edge’s default configuration contained Log4j 2 but was not vulnerable to Log4j 2 (CVE-2021-44228).
Apigee OPDK: Apigee OPDK’s default configuration contained Log4j 2 but was not vulnerable to Log4j 2 (CVE-2021-44228). The service “apigee-machinekey” includes Log4j 2 and does not process any user-provided input. It is not susceptible to the vulnerability CVE-2021-44228.
==== User Supplied Log4j 2 Instances ====
Apigee SaaS (X and Edge): Customers can upload vulnerable versions of Log4j 2 in their custom resources, but CVE-2021-4228 is mitigated due to Java Security Manager restrictions.
Log4j v1.x: Apigee Edge and Apigee OPDK contain Log4j 1.x and Log4j 2.x libraries. Log4j 1 is not part of this particular assessment. All instances of Log4j 1 will be upgraded across all Apigee products in upcoming releases to the latest version of Log4j 2. Upgrades to SaaS services and releases for OPDK are expected in January.
==== More Information ====
Information on this page is based on findings in our ongoing investigations.
Please see these helpful articles published to the Apigee Community: