Knowledge Base

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

ESX Server 3.0.2, Patch ESX-1003360: Security Updates to the Python Package (1003360)


Release Date: 02/20/08
Document Last Updated: 02/20/08

Product Versions ESX Server 3.0.2
Patch Classification Security
Supersedes None
Virtual Machine Migration or Reboot Required No
ESX Server Host Reboot Required No
PRs Fixed 224016
Affected Hardware N/A
Affected Software Python
RPMs Included python-2.2.3-6.8.i386.rpm
Related CVE numbers CVE-2006-7228, CVE-2007-2052, CVE-2007-4965


This patch provides service console updates for the Python package.  The patch fixes the following security issues:

  • An integer overflow issue with the way Python's Perl-Compatible Regular Expression (PCRE) module handles certain regular expressions. If a Python application uses the PCRE module to compile and execute untrusted regular expressions, it might be possible to cause the application to crash, or to execute arbitrary code with the privileges of the Python interpreter. 

    The Common Vulnerabilities and Exposures project ( has assigned the name CVE-2006-7228 to this issue.

  • A flaw in Python's locale module where strings generated by the strxfrm() function are not properly NULL-terminated. This might result in disclosure of data stored in the memory of a Python application using the strxfrm() function. 

    The Common Vulnerabilities and Exposures project ( has assigned the name CVE-2007-2052 to this issue.

  • Multiple integer overflow flaws in Python's imageop module that can allow an attacker to cause the application to crash, enter an infinite loop, or possibly execute arbitrary code with the privileges of the Python interpreter.

    The Common Vulnerabilities and Exposures project ( has assigned the name CVE-2007-4965 to this issue.



There are no symptoms for this security issue.

Deployment Considerations


Download Instructions

Download and verify the patch bundle as follows:

1.      Download patch ESX-1003360 from .

2.      Log in to the ESX Server service console as root.

3.      Create a local depot directory.

# mkdir -p /var/updates

Note: VMware recommends that you use the updates directory.

4.      Change your working directory to /var/updates.

# cd /var/updates

5.      Download the tar file into the /var/updates directory.

6.      Verify the integrity of the downloaded tar file:
# md5sum ESX-1003360.tgz

The md5 checksum output should match the following:

91d08543a3303827f3e07e12ffd45241 ESX-1003360.tgz

7.      Extract the compressed tar archive:

# tar -xvzf ESX-1003360.tgz

8.      Change to the newly created directory, /var/updates/ESX-1003360:

# cd ESX-1003360

Installation Instructions

Note: All virtual machines on the host must be either shut down or migrated using VMotion before applying the patch.  A reboot of the ESX Server host is required after applying this patch.


After you download and extract the archive, and if you are in the directory that you previously created, use the following command to install the update:

# esxupdate update

To run esxupdate from a different directory, you must specify the bundle path in the command:

# esxupdate -r file://<directory>/ESX-1003360 update

For example, if the host is called depot:

# esxupdate -r file:///depot/var/updates/ESX-1003360 update

During the update process, logs appear on the terminal. You can specify the verbosity of esxupdate logs by using the -v option as shown below.

# esxupdate -v 10 file://<directory>/ESX-1003360 update

For more information how to use esxupdate, see the Patch Management for ESX Server 3 tech note at .



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.


  • 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