You're viewing **Apigee Edge** documentation.
[Go to the
**Apigee X** documentation](http://cloud.google.com/apigee/docs). info
On June 27, 2022, we released a new version of Apigee Edge for Private Cloud.
**Note:** This version will be supported until June 27, 2023.
> [!NOTE]
> **Note about the Apache Log4j vulnerability:**
>
>
>
> Edge for Private Cloud's default configuration contains Log4j 2 but
> is not vulnerable to Log4j 2
> ([CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228)).
>
> Likewise, Edge for Private Cloud is not affected by the
> related vulnerability in Apache Log4j-1.x, which is shipped with ZooKeeper. That
> vulnerability requires a
> specific configuration of Log4j-1.x that Edge for Private Cloud
> does not ship as a default configuration. Therefore the vulnerability is not
> exploitable in Edge for Private Cloud.
> [!NOTE]
> For more information, see the following resources:
>
> - *[Edge for Private Cloud 4.51.00
> documentation](https://docs.apigee.com/private-cloud/v4.51.00)*
> - *Questions or issues?* Contact [Apigee Edge Support](https://docs.apigee.com/api-platform/troubleshoot/support)
> - *[Edge for Private Cloud support timeline](https://docs.apigee.com/release/apigee-edge-release-process#apigee-edge-for-private-cloud-support-timeline)*
> - *Release notifications* : See [Get Apigee Edge release notifications](https://docs.apigee.com/release/get-release-notifications)
## Update procedure
Updating this release will update the components in the following list of RPMs:
- edge-gateway-4.51.00-0.0.60169.noarch.rpm
- edge-management-server-4.51.00-0.0.60169.noarch.rpm
- edge-message-processor-4.51.00-0.0.60169.noarch.rpm
- edge-postgres-server-4.51.00-0.0.60169.noarch.rpm
- edge-qpid-server-4.51.00-0.0.60169.noarch.rpm
- edge-router-4.51.00-0.0.60169.noarch.rpm
- apigee-mirror-4.51.00-0.0.1028.noarch.rpm
- apigee-configutil-4.51.00-0.0.616.noarch.rpm
- apigee-provision-4.51.00-0.0.619.noarch.rpm
- apigee-adminapi-4.51.00-0.0.609.noarch.rpm
- edge-analytics-4.51.00-0.0.40065.noarch.rpm
- apigee-cassandra-2.1.22-0.0.2530.noarch.rpm
- apigee-cassandra-client-2.1.22-0.0.2515.noarch.rpm
You can check the RPM versions you currently have installed, to see if they
need to be updated, by entering:
```
apigee-all version
```
To update your installation, perform the following procedure on the Edge nodes:
1. On all Edge nodes:
1. Clean the Yum repos:
```
sudo yum clean all
```
2. Download the latest Edge 4.51.00 `bootstrap_4.51.00.sh` file to `/tmp/bootstrap_4.51.00.sh`:
```
curl https://software.apigee.com/bootstrap_4.51.00.sh -o /tmp/bootstrap_4.51.00.sh
```
3. Install the Edge 4.51.00 `apigee-service` utility and dependencies:
```
sudo bash /tmp/bootstrap_4.51.00.sh apigeeuser=uName apigeepassword=pWord
```
where uName and pWord are the username and password you received from Apigee.
If you omit pWord, you will be prompted to enter it.
4. Use the `source` command to execute the apigee-service.sh script:
```
source /etc/profile.d/apigee-service.sh
```
2. Update the apigee-provision utility on the Management Server:
```
/opt/apigee/apigee-service/bin/apigee-service apigee-provision update
```
3. Update the apigee-adminapi utility:
```
/opt/apigee/apigee-service/bin/apigee-service apigee-adminapi update
```
4. Update apigee-config util:
```
/opt/apigee/apigee-service/bin/apigee-service apigee-configutil update
```
5. Update all Cassandra nodes:
```
/opt/apigee/apigee-setup/bin/update.sh -c cs -f configFile
```
6. On all Edge nodes, execute the `update.sh` script for the edge process:
```
/opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
```
## Security issues fixed
The following is a list of known security issues that have been fixed in this release.
To avoid these issues, install the latest version of Edge Private Cloud.
| Issue ID | Description |
|---|---|
| 230857841 | A security issue related to [CVE-2022-22950](https://nvd.nist.gov/vuln/detail/CVE-2022-22950) has been fixed by upgrading spring version used in analytics to 5.3.20. |
| 234175444 | A security issue related to [CVE-2019-2708](https://nvd.nist.gov/vuln/detail/CVE-2019-2708) has been fixed by updating libdb artifacts for RHEL-8 (in apigee-thirdparty) to 5.3.28-42. |
## Changes to
[supported software](https://docs.apigee.com/release/supported-software#apigeeedgeforprivatecloudsupportedversions)
There are no changes to supported software in this release.
## Deprecations and retirements
There are no new deprecations or retirements in this release.
## New features
There are no new features in this release.
## Bug fixes
This section lists the Private Cloud bugs that were fixed in this release.
| Issue ID | Description |
|---|---|
| 234512031 | **Upgraded spring jars to 5.3.20 to address vulnerabilities.** |
| 169680013 | **Added property `conf_allowed_extensions` to control or whitelist files to check and print delta log.** This property contains the list of file extensions to print delta log. By default, the following file types/extensions are allowed to print delta log: sh, xml, properties, conf, key, config, json, yaml, yml, policy, toml. |
| 229306045 | **Added new utilities in apigee-adminapi to add and remove AX group properties. Modified apigee-provision so onboarding new AX groups have consumer-type property set appropriately.** |
| 230758130 | **Added legacy option to nodetool to maintain compatibility with latest version of Java 8** |
| 234043195 | **`apigee-mirror` was creating directories with incorrect permissions, causing errors when the synchronized repo was served with nginx.** This has been fixed |
| 235390529 | **Improved deployment performance of management server, reducing number of hits to Cassandra.** This improves performance for deployment operations in environments with a large number of deployed proxies |
| 233207795 | **Edge supported ciphers provides limited options and no ability to limit ciphers outside of a hard coded list** This has been fixed. While configuring TLS for management API, ciphers which are blacklisted and whitelisted are no longer filtered by ciphers listed by Apigee. Instead, the lists specified in these configs are directly applied. You can revert this to the prior behavior of Apigee filtered cipher list by setting `config conf_webserver.ssl.apigee.cipher.suites.enforce=true` in management server. |
## Known issues
See [Known issues with Edge for Private Cloud](https://docs.apigee.com/release/known-issues#private-cloud)
for a complete list of known issues.