VMware Aria Operations 8.17 Hot Fix 1 is a public Hot Fix that addresses the following issues:
Reads per second(IOPS) has increased due to the Pricing calculation
Property last value timestamp is incorrect in the property cache after upgrading to 8.15, 8.17
[SDK]: broken compatibility
[Analytics] Analytics upcoming is failing with "RunTimeException"
Chargeback: Migration: Exception on multi node setup during policies migrate
OpenSSL vulnerability
Payload Template: Need to change the text of Object Content
Collection fails by newly added node and "Unknown adapter type is specified" error is shown
[Cost-driver] Selected hosts are getting sorted on top as per selection instead of maintaining the real-order while selecting individual server for customization
Fix vSAN Performance API Request Parameters
The following CVEs have been resolved as of version 8.17 Hot Fix 1:
Note: Inclusion of a given CVE in the following table does not imply exploitability of said CVE.
Component Name
CVE
commons-beanutils
CVE-2019-10086
linux_kernel
CVE-2023-52434
CVE-2024-22099
CVE-2024-23307
CVE-2024-26584
CVE-2024-26688
CVE-2024-26733
CVE-2024-26735
CVE-2024-26736
CVE-2024-26747
CVE-2024-26751
CVE-2024-26754
CVE-2024-26763
CVE-2024-26764
CVE-2024-26772
CVE-2024-26773
CVE-2024-26777
CVE-2024-26779
CVE-2024-26782
CVE-2024-26791
CVE-2024-26793
CVE-2024-26795
CVE-2024-26801
CVE-2024-26804
CVE-2024-26805
openssl
CVE-2022-4304
CVE-2023-0215
CVE-2023-0286
CVE-2023-0464
CVE-2023-0465
CVE-2023-0466
Resolution
VMware Aria Operations 8.17 Hot Fix 1 can be applied to any 8.17.x environment. Note: Upgrading from older versions directly to this Hot Fix is not supported. You must upgrade to 8.17.x before applying this Hot Fix.
Log in to the primary node VMware Aria Operations Administrator interface of your cluster at https://primary-node-FQDN-or-IP-address/admin.
Click Software Update in the left panel.
Click Install a Software Update in the main panel.
Follow the steps in the wizard to locate and install your PAK file.
Install the product update PAK file. Wait for the software update to complete. When it does, the Administrator interface logs you out.
Log back into the primary node Administrator interface. The main Cluster Status page appears and cluster goes online automatically. The status page also displays the Bring Online button, but do not click it.
Clear the browser caches and if the browser page does not refresh automatically, refresh the page. The cluster status changes to Going Online. When the cluster status changes to Online, the upgrade is complete.
Note: If a cluster fails and the status changes to offline during the installation process of a PAK file update then some nodes become unavailable. To fix this, you can access the Administrator interface and manually take the cluster offline and click Finish Installation to continue the installation process.
Click Software Update to check that the update is done. A message indicating that the update completed successfully appears in the main pane.
Once the update is complete delete the snapshots you made before the software update.