Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

VMware ESX 4.1 Patch ESX410-201211402-SG: Updates bind-libs and bind-utils RPMs (2036262)

Details

Product Version
ESX 4.1
Patch Classification
 Security
See KB 2014447 if using Update Manager 5.0
Build Information
For build information, see KB 2036254.
Host Reboot Required
Yes
Virtual Machine Migration or Shutdown Required
Yes
PRs Fixed
895967
Affected Hardware
N/A
Affected Software
N/A
VIBs Included
  • bind-libs
  • bind-utils
    • Related CVE numbers
    CVE-2012-1033, CVE-2012-1667, and CVE-2012-3817

    Solution

    Summaries and Symptoms

    The ESX service console bind packages are updated to the following versions:

    • bind-libs-9.3.6-20.P1.el5_8.2
    • bind-utils-9.3.6-20.P1.el5_8.2
    These updates fix multiple security issues. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2012-1033, CVE-2012-1667, and CVE-2012-3817 to these issues.

     

    Deployment Considerations

    None beyond the required patch bundles and reboot information listed in the table above.

    Patch Download and Installation

    See the VMware vCenter Update Manager Administration Guide for instructions on using Update Manager to download and install patches to automatically update ESX 4.1 hosts.

    To update ESX 4.1 hosts when not using Update Manager, download the patch ZIP file from http://support.vmware.com/selfsupport/download/ and install the bulletin using esxupdate from the command line of the host. For more information, see the ESX 4.1 Patch Management Guide.

    Request a Product Feature

    To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

    Feedback

    • 0 Ratings

    Did this article help you?
    This article resolved my issue.
    This article did not resolve my issue.
    This article helped but additional information was required to resolve my issue.
    What can we do to improve this information? (4000 or fewer characters)
    • 0 Ratings
    Actions
    KB: