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 Server 3.5, Patch ESX350-200806404-SG: Security Updates to WebAccess Components Tomcat and JRE (1005219)

Details

Release Date: 16 JUNE 2008
Document Last Updated: 16 JUNE 2008

 

Download Size:
50MB
Download Filename:
ESX350-200806404-SG.zip
md5sum:
669e97880a21cce13eb7e9051f403162


Product Versions ESX Server 3.5
Patch Classification Security
Supersedes ESX350-200803215-UG
Requires ESX350-200805502-BG
Virtual Machine Migration or Reboot Required No
ESX Server Host Reboot Required No; restart WebAccess
PRs Fixed 259477, 259485
Affected Hardware N/A
Affected Software N/A
RPMs Included VMware-webCenter-esx
Related CVE numbers Referenced, below


Solution

Summaries and Symptoms

Issues fixed in this patch (and their relevant symptoms, if applicable) include:

Deployment Considerations

None beyond the required patch bundles and reboot information listed in the table, above.
 
To restart WebAccess:
  1. Log in to the service console as root.
  2. Run the command:
    service vmware-webAccess restart

Patch Download and Installation

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

To update ESX Server 3.5 hosts when not 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.

Keywords

esx35p05

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 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)
  • 1 Ratings
Actions
KB: