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 3.5, Patch ESX350-201008410-SG: Updates samba (1026134)

Details

Release Date: September 1, 2010

Download Size:
21.7 MB

Download Filename:

ESX350-201008410-SG.zip

md5sum:

c5224cf4218a3636b70207b8d269d024

Product Versions	ESX 3.5
Build	283373
Patch Classification	Security
Supersedes	ESX350-200712402-SG ESX350-200802415-SG ESX350-200808218-UG
Requires	ESX350-200911202-UG
Virtual Machine Migration or Reboot Required	No
Host Reboot Required	No
PRs Fixed	571967
Affected Hardware	None
Affected Software	None
RPMs Included	samba-3, samba-client, samba-common
Related CVE Numbers	CVE-2010-2063

Solution

Summaries and Symptoms

The service console RPMs for samba are updated to samba-3.0.9-1.3E.17vmw, samba-common-3.0.9-1.3E.17vmw, and samba-client-3.0.9-1.3E.17vmw. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-2063 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 vCenter Update Manager Administration Guide for instructions on using Update Manager to download and install patches to automatically update ESX 3.5 hosts.

To update ESX 3.5 hosts without using Update Manager, download the most recent patch bundle from http://www.vmware.com/download/vi/vi3_patches_35.html and install the bundle using esxupdate from the command line of the host. For more information, see the ESX Server 3 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

1 2 3 4 5
1 Ratings

1 2 3 4 5
1 Ratings

Actions

Bookmark Document

KB:

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)