Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

Fix for CVE-2014-0224 (OpenSSL Man in the middle) on VMWare ESX 4.1?

Posted on 2015-02-13
2
373 Views
Last Modified: 2015-02-13
Hi,

Does anyone know if VMWare ever released a patch to address the Open SSL man-in-the-middle vulnerability described in  CVE-2014-0224 for ESX 4.1?  All I've been able to find on The Google are references to patches released for ESX 5.5.  Is there something I'm missing?  I'd like to resolve that issue on our ESX 4.1 servers but I'm not looking to have to move all of them up to 5.5.

Thanks!
Matt
0
Comment
Question by:jdissupport
2 Comments
 
LVL 119

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points
ID: 40608672
ESX 4.1 -went - The End of General Support Life date remains May 21, 2014.

see here

End of Availability and End of Support Life for ESX 4.x and VMware Management Assistant 1.0 and 4.0 (2039567)

see
Support Policies

No more Security patches will be released for ESX 4.1.

Time to consider upgrading to a supported platform.
0
 

Author Closing Comment

by:jdissupport
ID: 40608694
Dang, I knew someone was going to say that :P
0

Featured Post

Portable, direct connect server access

The ATEN CV211 connects a laptop directly to any server allowing you instant access to perform data maintenance and local operations, for quick troubleshooting, updating, service and repair.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article, I will show you HOW TO: Install VMware Tools for Windows on a VMware Windows virtual machine on a VMware vSphere Hypervisor 6.5 (ESXi 6.5) Host Server, using the VMware Host Client. The virtual machine has Windows Server 2016 instal…
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to convert virtaul disk file formats and how to rename virtual machine files on datastores. Open vSphere Web Client: Review VM disk settings: Migrate VM to new datastore with a thick provisioned (lazy zeroed) disk format: Rename a…
Teach the user how to use configure the vCenter Server storage filters Open vSphere Web Client:  Navigate to vCenter Server Advanced Settings: Add the four vCenter Server storage filters: Review the advanced settings: Modify the values of the four v…

839 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question