• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 801
  • Last Modified:

Extract VMWare-esx-vmx-64607 rpm from existing ESX


I've just installed an rpm ( VMWare-esx-vmx-3.5.0-158869.i386.rpm )
and this caused the entire ESX/VMWare to panic/crash whenever a
VM in this VMWare is started.

I've just done "rpm -e --nodeps -allmatches VMware-esx-vms-3.5.-158869)
and would like to put back the old rpm 64607 :


However, I could not find 64607 from anywhere (requires a code), so I'll
need to extract this 64607 rpm from my other ESX servers : is this possible
& what's the command.

If it's not possible to build the 64607 rpm from an existing ESX which has
not been patched yet, appreciate if someone can point me to where I could
download it

1 Solution
You want to downgrade from 3.5U4 to 3.5U0?

Doesn't sound like a good idea since lots of things have been changed since then and you should probably file a SR with VMware about your issue.

If you still want to downgrade it would proabably be easiest to boot from the 3.5 CD and install ESX over again. It will not destroy your virtual machines, but not your network config before doing this as you will have to set it up all over again.

sunhuxAuthor Commented:
Hi Larstr

I did not give you the full description.  Well, I'm actually trying to address the following
security vulnerability :

=============I got the following fr our security team: ================


I'm trying to address the vulnerability (see below) given by security team.

Our ESX 3.5 is affected (ESX 2.5 is Ok).  I've got the .rpm patch file.
Do I install using
   rpm -Uvh patchfile.rpm
   rpm -ivh patchfile.rpm

What's the difference between the two?  Redhat suggested to me to use
"rpm -ivh" to install the .rpm packages from their site but I've seen some
places using "rpm -U package.rpm"

===========Reply from another thread : ===============

A vulnerability was reported in VMware. A local user on the guest operating system can obtain elevated privileges on the target host system.

A local user can exploit a flaw in the virtual machine display function to execute arbitrary code on the target host system.

VMware Workstation, Player, ACE, Server, Fusion, ESXi, and ESX are affected.

[Affected System]
Workstation 6.5.x any 6.5.2 build 156735 or later
Workstation 6.0.x any upgrade to at least 6.5.2

Player 2.5.x any 2.5.2 build 156735 or later
Player 2.0.x any upgrade to at least 2.5.2

ACE 2.5.x Windows 2.5.2 build 156735 or later
ACE 2.0.x Windows upgrade to at least 2.5.2

Server 2.x any 2.0.1 build 156745 or later
Server 1.x any 1.0.9 build 156507 or later

Fusion 2.x Mac OS/X 2.0.4 build 159196 or later

ESXi 3.5 ESXi ESXe350-200904201-O-SG

ESX 3.5 ESX ESX350-200904201-SG
ESX 3.0.3 ESX ESX303-200904403-SG
ESX 3.0.2 ESX ESX-1008421

[Impact Analysis]
A local user on the guest operating system can obtain privileges on the target host system.

The vendor released a fix and an advisory.
Please see the references for more information.



I don't understand...

You say this is a VMware ESX 3.5 host, right?  Why would you be installing a RedHat RPM?  \

The patch you need is from VMware, and is installed on the VMware host using the service console, not on the RedHat guest.
It should be file ESX350-20094201-SG.ZIP which contains the file VMware-esx-vmx-3.5.0-158869.i386.rpm

According to the KB article, you're supposed to either use the VI Update Manager or install the package using esxupdate from the command line.  http://kb.vmware.com/kb/1009852

Featured Post

Restore individual SQL databases with ease

Veeam Explorer for Microsoft SQL Server delivers an easy-to-use, wizard-driven interface for restoring your databases from a backup. No expert SQL background required. Web interface provides a complete view of all available SQL databases to simplify the recovery of lost database

Tackle projects and never again get stuck behind a technical roadblock.
Join Now