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.0.3, ESX303-200808402-SG: Perl Security Update to Service Console Package (1006033)

Details

Release Date: 08/28/08
Document Last Updated: 08/28/08
 
a6734a3438da0492b3cad6c0bb462da4


Product Versions
ESX Server 3.0.3
Patch Classification
Security
Supersedes
None
Requires
None
Virtual Machine Migration or Reboot Required
No
ESX Server Host Reboot Required
No
PRs Fixed
289419
Affected Hardware
N/A
Affected Software
Perl
RPMs Included
perl-5.8.0-98.EL3
Related CVE numbers
CVE-2008-1927

 

Solution

Summaries and Symptoms

This patch fixes a flaw in Perl's regular expression engine with Unicode characters, which might trigger a buffer overflow, causing Perl to crash, or possibly execute arbitrary code with the privileges of the user running Perl.
 
The Common Vulnerabilities and Exposures project (cve.mitre.org) assigned the name CVE-2008-1927 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 Update Manager Administration Guide for instructions on using VMware Update Manager to download and install patches to automatically update ESX Server 3.0.3 hosts.

To update ESX Server 3.0.3 hosts when not using VMware Update Manager, download the most recent patch bundle from http://support.vmware.com/selfsupport/download/  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

esxpatch;esx303

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: