The Indian Computer Emergency Response Team (CERT-IN) has issued an alert on vulnerabilities in VMware Aria Operations.
Versions of VMware Aria Operations prior to 8.12 are vulnerable to cyberattacks due to the high-severity vulnerabilities published in the CERT-IN vulnerability note CIVN-2023-1032, with a severity rating of High.
VMware has issued patches for these vulnerabilities.
Details about vulnerabilities inVMware
The company advisory about the vulnerabilities in VMware stated that the CVSSv3 range of the flaws was between 6.4 and 8.8. The flaws were alerted to the company by MoyunSec Vlab and Bing for which it made updates and workarounds available.
The vulnerabilities in VMware listed in the CERT-IN alert were as follows:
- CVE-2023-20877 was a privilege escalation flaw with a CVSSv3 base score of 8.8. This flaw can allow hackers to run malicious codes on unpatched devices.
- CVE-2023-20878 was a moderate-severity deserialization bug with a CVSSv3 base score of 6.6. If the product is not updated, hackers can run arbitrary codes just like the above flaw. They can also disrupt the system.
- CVE-2023-20879 was a moderate-severity bug that allowed local privilege escalation. It had a CVSSv3 base score of 6.7. Hackers may gain administrative privileges like the above vulnerability and run arbitrary codes.
- CVE-2023-20880 was also a moderate-severity bug that allowed local privilege escalation. It had a CVSSv3 base score of 6.4. Hackers can escalate privileges to the root and cause more damage with escalated privileges on unpatched devices.
Version 8.10 Hot Fix 4 to address the vulnerabilities in VMware
Patches were made available for the vulnerabilities in VMware, which should be upgraded by users to avoid leaving the product and device exposed to hackers.
Vulnerabilities are a common and major cause of exploitation as hackers are always on the lookout for flaws that lets them make their way into systems. One unpatched system endangers the entire network of even patched software including devices that are connected to it.
Called hot fix 4 (91852), VMware made patches available for all the users. The fixes page was updated on May 11, 2023, and it addressed the following issues:
- VMware chargeback bills creating inaccurate results.
- Bills showing only Tier 1 value excluding Tier 2 on vapp.
“vRealize Operations 8.10 Hot Fix 4 can be applied to any 8.10 environment. Upgrading from older versions directly to this Hot Fix is not supported. You must upgrade to 8.10 before applying this Hot Fix,” the VMware patch report read followed by instructions on how to complete the software update.
The vulnerabilities in VMware can be patched by first downloading the minimum version required for the hot fix. Thereafter, a user may select the following options as recommended in the company alert:
- Choose vRealize Operations Manager for Product
- Opt for 10 for the version
- Select Search for the right version and log in to the primary node vRealize Operations Manager Administrator interface.
- Opt for Software Update as shown on the individual device.
- And go for the Install a Software Update
One will have to locate the PAK file and wait for the software to update following which the user will be logged out. Once the upgrade is successfully completed, users will see the cluster status changed to ‘Online.’
To make sure the upgrade is completed, one may have to clear the browser caches and see that the page is refreshed.
Vulnerability management and cybersecurity
While vendors like VMware promptly addresses and issues alerts on vulnerabilities, users often lag in patching their systems, The Cyber Express reported earier.
According to Dan Richings, SVP – Global Presales and Solutions Engineering at Adaptiva, companies face several challenges when it comes to patch management.
One challenge is the overwhelming influx of patches, leading to a backlog that needs prioritization based on usage and security severity. Remote work and the use of personal devices add complexity to securing and monitoring updates.
Communication issues arise when different IT teams handle various tasks, and slow change management processes and flawed patches further impede the patching process. Additionally, many organizations still rely on manual patching, which consumes significant time and resources.
