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.0, Patch ESX400-200912404-SG: Updates DHCP (1016294)

Details

Release Date: January 5, 2010
Download Size:
473.5MB
Download Filename:
ESX400-200912001.zip
md5sum:
78c6cf139b7941dc736c9d3a41deae77
sha1sum:
36df3a675fbd3c8c8830f00637e37ee716bdac59

Product Versions ESX 4.0
Build 219382
Also see KB 1012514.
Patch Classification Security
Host Reboot Required No
Virtual Machine Migration or Shutdown Required No
PRs Fixed 448120
Affected Hardware N/A
Affected Software N/A
Modified VIBs Included dhcp-cos
Related CVE numbers CVE-2009-0692

Solution

Summaries and Symptoms

This patch contains a fix for a security vulnerability in the ISC third-party DHCP client. This vulnerability allows for code execution in the client by a remote DHCP server through a specially crafted subnet-mask option.

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

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.0 hosts.

To update ESX 4.0 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 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: