Mar 10

Configuring OpenSSL for installation and configuration of CA signed certificates in the vSphere environment (2015387)

Purpose

This article guides you through the installation and configuration of OpenSSL. You may want to install and configure OpenSSL to be able to create custom certificates for vSphere environments. It also helps to eliminate common causes for problems and ensure that the requests generated are appropriate for vSphere environments.

Resolution

Overview

OpenSSL can be used for creating certificate requests and also as a certificate authority. Although the steps that are used to generate the certificate are different, the setup and configuration steps are the same as the certificates that vSphere uses are X.509 v3 SSL certificates. Only the way in which the actual certificate is generated is different.

Setup

Important: Ensure that you are using OpenSSL version 0.9.8. If you do not use this version, the SSL implementation will fail.To setup OpenSSL:

  1. Ensure that the Microsoft Visual C++ 2008 Redistributable Package (x86) is installed on the system on which you want to generate the requests. To download the package, see the Microsoft Download Center.
  2. Download the Shining Light Productions installer for OpenSSL x86 version 0.98r or later at http://www.slproweb.com/products/Win32OpenSSL.html. This is a software developed from the OpenSSL Project.
  3. Launch the installer and proceed through the installation and note the appropriate directory for later use. By default, it is located at c:\OpenSSL-Win32.After this program is installed, you must configure it to issue vSphere certificates.Note: The preceding links were correct as of July 29, 2013. If you find a link is broken, provide feedback and a VMware employee will update the link.

Configuration

To configure OpenSSL follow these steps:
  1. Take a backup of the openssl.cfg file. By default, this file is located at the c:\OpenSSL-Win32\bin directory.
  2. Delete the contents of the file and replace with:Note: Replace the code in Red with the details of the server that you are configuring.[ req ]
    default_bits = 2048
    default_keyfile = rui.key
    distinguished_name = req_distinguished_name
    encrypt_key = no
    prompt = no
    string_mask = nombstr
    req_extensions = v3_req[ v3_req ]
    basicConstraints = CA:FALSE
    keyUsage = digitalSignature, keyEncipherment, dataEncipherment
    extendedKeyUsage = serverAuth, clientAuth
    subjectAltName = DNS:vc50, IP:10.0.0.10, DNS:vc50.vmware.com[ req_distinguished_name ]
    countryName = US
    stateOrProvinceName = NY
    localityName = New York
    0.organizationName = VMWare
    organizationalUnitName = vCenterInventoryService
    commonName = vc50.vmware.com
  3. Save and close the file.The installation is now set to configure a certificate for the server that you have entered in the file. You can repeat this configuration by creating separate files for each server request or by not specifying a value. If you do not specify a value, OpenSSL prompts you for the information.Note: The preceding modified file will not prompt you for information because all information is configured within the file.

Additional Information

Posted in Uncategorized
Mar 10

New VMware Security Advisory VMSA-2013-0016

Today VMware has released the following new security advisory:

VMSA-2013-0016

The advisory documents CVE-2013-5973 “VMware ESXi and ESX unauthorized file access through vCenter Server and ESX”. This issue may allow certain unprivileged users on vCenter Server access to arbitrary files on ESXi/ESX and may allow local unprivileged users on ESX (i.e. ESX 4.0 and ESX 4.1) access to arbitrary files. Modification of files on ESXi or ESX may allow for code execution after a host reboot.

Please sign up to the Security-Announce mailing list to receive new and updated VMware Security Advisories.

Customers should review the security advisory and direct any questions to VMware Support.

Posted in Uncategorized
Mar 10

VMSA-2013-0016

VMware Security Advisories

VMSA-2013-0016

VMware ESXi and ESX unauthorized file access through vCenter Server and ESX
1. Summary
VMware ESXi and ESX unauthorized file access through vCenter Server and ESX
2. Relevant releases

VMware ESXi 5.5 without patch ESXi550-201312001
VMware ESXi 5.1 without patch ESXi510-201310001
VMware ESXi 5.0 without patch update-from-esxi5.0-5.0_update03
VMware ESXi 4.1 without patch ESXi410-201312001
VMware ESXi 4.0 without patch ESXi400-201310001

VMware ESX 4.1 without patch ESX410-201312001
VMware ESX 4.0 without patch ESX400-201310001

3. Problem Description
a. VMware ESXi and ESX unauthorized file access through vCenter Server and ESX

VMware ESXi and ESX contain a vulnerability in the handling of certain Virtual Machine file descriptors. This issue may allow an unprivileged vCenter Server user with the privilege “Add Existing Disk” to obtain read and write access to arbitrary files on ESXi or ESX. On ESX, an unprivileged local user may obtain read and write access to arbitrary files. Modifying certain files may allow for code execution after a host reboot.

Unpriviledged vCenter Server users or groups that are assigned the predefined role “Virtual Machine Power User” or “Resource Pool Administrator” have the privilege “Add Existing Disk”.

The issue cannot be exploited through VMware vCloud Director.

Workaround

  • A workaround is provided in VMware Knowledge Base article 2066856.

Mitigation

  • In a default vCenter Server installation no unprivileged users or groups are assigned the predefined role “Virtual Machine Power User” or “Resource Pool Administrator”.
  • Restrict the number of vCenter Server users that have the privilege “Add Existing Disk”.

VMware would like to thank Shanon Olsson for reporting this issue to us through JPCERT.

The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-5973 to this issue.

Column 4 of the following table lists the action required to remediate the vulnerability in each release, if a solution is available.

Known Issues (*)

Deploying these patches does not remediate the issue if the ESXi or ESX file /etc/vmware/configrules has been modified manually (modifying this file is uncommon). Customers who have modified this file should apply the workaround after installing the patch.

After deploying the patches, Virtual Machines that have their names ending in “-flat”, “-rdm” or “-rdmp” will no longer power on. See the VMware Knowledge Base article listed under “Workaround” for a solution.

4. Solution

Please review the patch/release notes for your product and version and verify the checksum of your downloaded file.
ESXi and ESX
——————

https://www.vmware.com/patchmgr/download.portal

ESXi 5.5
——————
File: ESXi550-201312001.zip
md5sum: 549b5eb75f1d4d937019d2c28e15a4fe
sha1sum: c2656b25e2a85799d4aa79ded942d4c322e9487a
http://kb.vmware.com/kb/2063795
ESXi550-201312001 contains ESXi550-201312101-SG

ESXi 5.1
——————
File: ESXi510-201310001.zip
md5sum: 00b6a97b3042dc45da52e20b67666387
sha1sum: 8b0e2e832d0c603991718da17e1f73de4f0969cc
http://kb.vmware.com/kb/2053402
ESXi510-201310001 contains ESXi510-201310101-SG

ESXi 5.0
——————
File: update-from-esxi5.0-5.0_update03.zip
md5sum: 7e6185fa3238a4895613b39e57a2a94b
sha1sum: aa3929d2c8183aeaecdc238cbbf4d270bd70dd07
http://kb.vmware.com/kb/2055559
update-from-esxi5.0-5.0_update03 contains ESXi500-201310101-SG

ESXi 4.1
——————
File: ESXi410-201312001.zip
md5sum: f85c0c449513b88b22f19a5f11966d5e
sha1sum: cfde5abbef77976b76d55813ae1e7bbbbca25b7b
http://kb.vmware.com/kb/2061210
ESXi410-201312001 contains ESXi410-201312401-SG

ESXi 4.0
——————
File: ESXi400-201310001.zip
md5sum: 3075bce1b19a52b053a5dc18d06d40e0
sha1sum: 19952da0dd9f81ea299cb8ae6c462f11566b56e0
http://kb.vmware.com/kb/2059496
ESXi400-201310001 contains ESXi400-201310401-SG

ESX 4.1
——————
File: ESX410-201312001.zip
md5sum: c35763a84db169dd0285442d4129cc18
sha1sum: ee8e1b8d2d383422ff0dde04749c5d89e77d8e40
http://kb.vmware.com/kb/2061209
ESX410-201312001 contains ESX410-201312401-SG

ESX 4.0
——————
File: ESX400-201310001.zip
md5sum: 9d47cf815ed142a17f97002379b5e386
sha1sum: 91082ec4263333f9b996883cb53dbe9aab7a88b5
http://kb.vmware.com/kb/2059495
ESX400-201310001 contains ESX400-201310401-SG

6. Change log
2013-12-22 VMSA-2013-0016
Initial security advisory in conjunction with the release of ESXi 5.5 patches on 2013-12-22
7. Contact

E-mail list for product security notifications and announcements:
http://lists.vmware.com/cgi-bin/mailman/listinfo/security-announce

This Security Advisory is posted to the following lists:

* security-announce at lists.vmware.com
* bugtraq at securityfocus.com
* full-disclosure at lists.grok.org.uk

E-mail: security at vmware.com
PGP key at:  http://kb.vmware.com/kb/1055

VMware Security Advisories
http://www.vmware.com/security/advisories

VMware security response policy
http://www.vmware.com/support/policies/security_response.html

General support life cycle policy
http://www.vmware.com/support/policies/eos.html

VMware Infrastructure support life cycle policy
http://www.vmware.com/support/policies/eos_vi.html

Posted in Uncategorized
Mar 10

VMware Security Hardening Guides

Security Hardening Guides provide prescriptive guidance for customers on how to deploy and operate VMware products in a secure manner. Guides for vSphere are provided in an easy to consume spreadsheet format, with rich metadata to allow for guideline classification and risk assessment. They also include script examples for enabling security automation. Comparison documents are provided that list changes in guidance in successive versions of the guide.

Hardening Guides

vSphere 6.5

vSphere 6.0

vSphere 5.5 Update 1

vSphere 5.5

vSphere 5.1

vSphere 5.0 and earlier

Other VMware Products

Rating: 5/5


Mar 09

vSphere 5.1 Update 1 Released!

VMware has just released the much anticipated Update 1 patch for vSphere 5.1 which includes several updates and bug fixes for both ESXi and vCenter Server 5.1. I highly encourage everyone to review the release notes for the complete list of resolved issues. While going through the ESXi 5.1 Update 1 release notes myself, I noticed a few resolved bugs that I had been following and thought I would highlight a few of them:

  • Reinstallation of ESXi 5.1 does not remove the Datastore label of the local VMFS of an earlier installation
    • Re-installation of ESXi 5.1 with an existing local VMFS volume retains the Datastore label even after the user chooses the overwrite datastore option to overwrite the VMFS volume.
  • resxtop fails when upgraded from vSphere 5.0 to vSphere 5.1
    • In vSphere 5.1, SSL certification checks are turned ON. This might cause resxtop to fail in connecting to hosts and displays an exception message similar the following: HTTPS_CA_FILE or HTTPS_CA_DIR not set. (More details about this issue can be found in this blog article)
  • Using the invoke-vmscript command displays an error
    • When you use the invoke-vmscript powercli command scripts on the virtual machine, the script fails with the following error message:

One interesting thing that caught my eye while going through the release note is the following:

  • Component-based logging and advanced configurations added to hostd log level
    • To avoid difficulties in getting appropriate logs during an issue, this release introduces component-based logging by dividing the loggers into different groups and prefixing them. Also, new advanced configuration allows you to change hostd log’s log level without restarting.

It looks like you now have the ability to configure granular log levels for various components within hostd which can better assist during troubleshooting and log collection. I will discuss how this works in more detail in another blog article.

There are many more resolved issues and you can check out the rest of the fixes in the ESXi 5.1 release notes.

Get notification of new blog postings and more by following vmware360 on Twitter: @vmware360

Posted in Uncategorized
Mar 09

VMware Virtual SAN Design and Sizing Guide

VSAN Sizing

vSAN Sizing

Now that we have officially launched Virtual SAN, its time for everyone to get up to speed with the some of the latest and greatest changes with regards to the new design and sizing considerations guidance for Virtual SAN.

Yesterday, we announced the official release time frame for the general availability of the product the week of March 10th as well as the items listed below:

    ■ 3 to 32 node cluster support
    ■ Maximum support of 3200 Virtual Machines
    ■ 2 Million IOPS performance capability
    ■ 4.4 Petabytes of Storage Capacity

Along with those changes and updates there are also some significant changes in the recommendation for the sizing of the flash layer for Virtual SAN. I highly recommend reviewing the white paper as the new sizing guidelines can have an impact on the overall investment and performance of the flash layer for Virtual SAN. The new design and sizing guide can be found and downloaded from the VMware Virtual SAN product page or directly from the link provided below:

Download

Download out the full VMware vSAN Design and Sizing Guide

Rating: 5/5


Posted in Uncategorized