ESX Virtualization

VMware ESXi, vSphere, VMware Backup, Hyper-V... how-to, videos....

Nakivo Backup and Replication - #1 Backup solution for Virtual, physical, cloud, NAS and SaaS

VMware vCenter Server 8.0 U1b resolves further upgrade issues and adds bunch of security patches

By | Last Updated:

Shares

Another new version for VMware vCenter Server 8.01b this time. After recent release of 8.0 U1a, this time, VMware adds more bug fixes and another batch of security patches so it is time and trigger another upgrade for infrastructure admins to keep their vSphere up-to-date.

Let's dive into the details. The vulnerabilities fixed are the follows:

  • This release resolves CVE-2023-20892, CVE-2023-20893, CVE-2023-20894, CVE-2023-20895, and CVE-2023-20896. For more information on these vulnerabilities and their impact on VMware products, see VMSA-2023-0014.

A bug few other fixes are resolved. VMware vCenter Server 8.0 Update 1b delivers bug fixes:

Quote:

  • vCenter 8.x installation might fail during firstboot with an error for a missing install parameter

    While installing vCenter 8.x, you might see the error cis.exceptions.InstallParameterException during the firstboot step due to a missing upgrade.import.directory install parameter. The error occurs if vCenter does not find the parameter due to VM restarts, or restores to a VM Snapshot without memory before running the firstboot configuration.

    This issue is resolved in this release. The fix makes sure that the upgrade.import.directory install parameter is correctly passed during vCenter installation.

  • Installation and upgrades to vCenter 8.0 Update 1 fail when a vCenter Single Sign-On domain contains uppercase letters

    If your vCenter Single Sign-On domain contains uppercase letters such as [email protected] or [email protected], installation, patching and upgrades to vCenter 8.0 Update 1 might fail. During installation or upgrade from an earlier version, in the install wizard, you see an error such as Failed to start the Workload Control Plane Service. During patching from 8.x, in the Virtual Appliance Management Interface, you see the error Exception occurred in postInstallHook. Messages in the /var/log/vmware/wcp/wcpsvc.log file shows a failure such as:

    2023-04-17T13:04:54.017Z error wcp [gcauth/gc_auth.go:94] Failed to parse VC JWKS: invalid character '<' looking for beginning of value

    2023-04-17T13:04:54.017Z error wcp [gcauth/gc_auth.go:59] Unable to get VC public key configuration : invalid character '<' looking for beginning of value

    2023-04-17T13:04:54.017Z fatal wcp [gcauth/gc_auth.go:47] Unable to get VC public key configuration : invalid character '<' looking for beginning of value

    You can see the case of an SSO domain by using the following command: /usr/lib/vmware-vmafd/bin/vmafd-cli get-domain-name --server-name localhost . Example output of the above command might be VSPHERE.LOCAL.

    This issue is resolved in this release.

  • If no vSphere vMotion bandwidth for migration of VMs with vGPUs is available, the vpxd service might fail at regular intervals

    If vpxd restarts during a migration of VMs with vGPUs and for some reason vSphere vMotion has no bandwidth available, vpxd might start failing on regular intervals.

    This issue is resolved in this release. If you already face the issue, restart the vpxd service, re-add ESXi hosts using the Quickstart workflow, and reconfigure the vSphere vMotion network to make sure bandwidth is available.

If you're working as an infrastructure admin or as a guy who maintains vSphere infrastructure, just head and download the latest upgrade for VMware vSphere. Don't forget to backup your vCenter server appliance (VCSA) before upgrading because one never knows what can happen.

Staying current with the latest release of VMware vSphere aids in meeting compliance and regulatory standards. Many industries have specific guidelines for data security and privacy, and by upgrading, you can align your infrastructure with these requirements, mitigating potential risks and avoiding penalties.

Upgrading to VMware vCenter Server 8.0 U1b can enhance the performance and stability of your virtualized environment. By leveraging the latest optimizations and bug fixes, you can ensure a smoother operation and reduce the likelihood of security-related issues caused by system instability.

Ransomware attacks have become increasingly sophisticated and devastating in recent years. These malicious attacks encrypt an organization's data, rendering it inaccessible until a ransom is paid. To combat this growing menace, VMware vSphere has several security features such as encrypted vMotion where data is encrypted while it is being migrated between hosts, providing an additional layer of protection against unauthorized access during the migration process.

Also, there is a Secure Boot ensures that only trusted software components are loaded during the boot process, preventing the execution of compromised or unauthorized code.

Another feature is vSphere Trust Authority which establishes a secure connection between vCenter Server and the ESXi hosts, ensuring the authenticity and integrity of the hosts. It safeguards against attacks that attempt to impersonate legitimate hosts or inject unauthorized changes.

Links

  • Download latest vSphere patch here.
  • Release notes here

Final Words

The threat landscape is ever-evolving, and organizations must remain proactive in their efforts to defend against ransomware attacks and other security threats. Upgrading to the latest release of VMware vCenter Server, such as VMware vCenter Server 8.0 U1b, is a critical step in fortifying your infrastructure.

By doing so, you gain access to enhanced security features, improved ransomware mitigation measures, and compliance with regulatory requirements. Ensure the safety, stability, and resilience of your virtualized environment by staying current with VMware vSphere and safeguarding your organization's valuable data.

More posts from ESX Virtualization:

Shares
Vote !

About Vladan SEGET

This website is maintained by Vladan SEGET. Vladan is as an Independent consultant, professional blogger, vExpert x16, Veeam Vanguard x9, VCAP-DCA/DCD, ESX Virtualization site has started as a simple bookmarking site, but quickly found a large following of readers and subscribers.

Connect on: Facebook. Feel free to network via Twitter @vladan.

Comments

  1. BennyRT2 says

    My lab is currently on 7.0u3k (Feb 2023 released).

    I’m researching a slew of upgrade paths for my lab. Looking at these from a very high level, I think I’m planning the upgrades in this order.

    Veeam (v11 to v12. Then after some time making sure v12 is stable… upgrading the Veeam12 DB from SQL Server to PostgreSQL)

    ESXi and VCSA to v8.0u1 (possible U2 by then)

    and then eventually the Win10 guests to Win11

    Its a real brain workout as I plan and document my best upgrade path.

    I just want to say that your website has really helped me alot and I appreciate it.