VMware Aria Operations for Logs 8.18 Hot Fix 1
Article ID: 373991
Updated On:
Products
VMware Aria Suite
Issue/Introduction
VMware Aria Operations for Logs 8.18 Hot Fix 1 is a public Hot Fix that addresses the following issues:
- Session TTL is not extended correctly for API Client. The API client fails to identify that the session was already expired (60 seconds) and does not extend the session before executing the API call.
- Aria Operations for Logs crashes due to race condition while trying to reconfigure a component within LI.
The following CVEs have been resolved as of version 8.18 Hot Fix 1:
Note: Inclusion of a given CVE in the following table does not imply exploitability of said CVE.
| Component Name | CVE |
| ch.qos.logback:logback-core | CVE-2021-42550 |
| CVE-2023-6378 | |
| cri-o | CVE-2024-5154 |
| curl | CVE-2023-46218 |
| CVE-2023-46219 | |
| glibc | CVE-2024-33599 |
| CVE-2024-33600 | |
| CVE-2024-33601 | |
| CVE-2024-33602 | |
| golang-runtime | CVE-2023-45288 |
| CVE-2023-45289 | |
| CVE-2023-45290 | |
| CVE-2024-24783 | |
| CVE-2024-24784 | |
| CVE-2024-24785 | |
| CVE-2024-24787 | |
| CVE-2024-24788 | |
| CVE-2024-24789 | |
| CVE-2024-24790 | |
| libssh2 | CVE-2023-48795 |
| linux_kernel | CVE-2024-26900 |
| CVE-2024-26945 | |
| CVE-2024-26996 | |
| CVE-2024-27019 | |
| CVE-2024-27398 | |
| CVE-2024-27407 | |
| CVE-2024-35848 | |
| CVE-2024-35947 | |
| CVE-2024-36902 | |
| CVE-2024-36971 | |
| CVE-2024-38583 | |
| CVE-2024-38662 | |
| CVE-2024-38780 | |
| CVE-2024-39292 | |
| CVE-2024-39475 | |
| CVE-2024-39476 | |
| CVE-2024-39480 | |
| CVE-2024-39489 | |
| CVE-2024-39493 | |
| openssh | CVE-2024-6387 |
Environment
VMware Aria Operations for Logs 8.18
Resolution
Download and install the correct Hotfix version that matches your version of VMware Aria Operations for Logs.
- Download the VMware Aria Operations for Logs 8.18 Hot Fix PAK file the link below.
Note: You will need to login to the portal in order to allow download of the file when using the direct links below.
| Release Name | Release Date | Build Number | File Name |
|---|---|---|---|
| Aria Operations for Logs 8.18.0 HF1 | 8/8/2024 | 24179185 | VMware-vRealize-Log-Insight-8.18.0-24179185.pak |
| AriaLCM-AriaLogs-8.18.0-HF1 | 8/8/2024 | 24179185 |
*vrlcm-vrli-8.18.0-HF1.patch |
* 'AriaLCM-AriaLogs-8.18.0-HF1' is to be used in Aria Suite Lifecycle Manager.
Prerequisites
- Create a snapshot or backup copy of the VMware Aria Operations for Logs virtual appliance(s)
- Obtain a copy of the VMware Aria Operations for Logs upgrade bundle .pak file for the release or hot fix you are upgrading to
- Verify that you are logged in to the VMware Aria Operations for Logs web user interface as a user with the Edit Admin permission. The URL format is https://log-insight-host, where log-insight-host is the IP address or host name of the primary node of the VMware Aria Operations for Logs virtual cluster.
- Make a note of any nodes you are upgrading that are in maintenance mode. When the upgrade is finished, you must move them from the state Connected to Maintenance mode.
Procedure
- Under Management, click Cluster.
- Click 'Upgrade Cluster' to upload the pak file.
- Accept the new EULA to complete the upgrade procedure.
- Reference Document Link: Upgrading VMware Aria Operations for Logs.
What to do next
-
- After the primary node upgrade process is complete, you can view the remaining upgrade process, which is automatic.
- Check for the email sent to the Admin to confirm the upgrade completed successfully.
- After upgrade, all nodes are brought online even if they were in maintenance mode before the upgrade. Move these nodes back to maintenance mode as needed.
- Remove the snapshots from the VMware Aria Operations for Logs appliance(s) within ~72 hours after a successful upgrade to avoid performance issues
Feedback
Yes
No
Powered by
