Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | [NEWS] SSL Sessions Not Authenticated By VMware VC Clients |
|---|---|
| Date: | 27 Nov 2006 14:08:20 +0200 |
The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com - - promotion The SecuriTeam alerts list - Free, Accurate, Independent. Get your security news from a reliable source. http://www.securiteam.com/mailinglist.html - - - - - - - - - SSL Sessions Not Authenticated By VMware VC Clients ------------------------------------------------------------------------ SUMMARY VMware VirtualCenter client does not verify the server's X.509 certificate when creating an SSL session, which allows remote malicious servers to spoof valid servers via a man-in-the-middle attack. DETAILS Vulnerable Systems: * VMware VirtualCenter client 2.x before 2.0.1 Patch 1 (Build 33643) * VMware VirtualCenter client 1.4.x before 1.4.1 Patch 1 (Build 33425) To ensure a secure channel of communication, you must be sure that any communication is with "trusted" sites whose identity you can be sure of. Both the client and server need certificates from a mutually-trusted Certificate Authority (CA). However, certificate verification is not enabled by default for the clients. After installing VirtualCenter 2.0.1 Patch 1 or VirtualCenter 1.4.1 Patch 1, you must specifically enable server-certificate verification on theWindows client hosts. VirtualCenter 2.0.1 Patch 1 and VirtualCenter 1.4.1 Patch 1 resolve an issue with server-certificate verification by VirtualCenter clients during the initial SSL handshake. Specifically, the x.509 certificate presented by a server to a client at the beginning of an SSL session is not verified. VirtualCenter 2.0.1 Patch 1 and VirtualCenter 1.4.1 Patch 1 resolve this issue for Windows client hosts. Solution: Note that installing the updated software does not, by default, enable authentication. For information about how to enable this new optional capability, see Knowledge Base (KB) article 4646606, " <http://kb.vmware.com/kb/4646606 > Enabling Server- Certificate Verification for Virtual Infrastructure Clients." Client hosts include: * VirtualCenter Server host, which operates as a client to each of the servers that it manages; VirtualCenter Server 2.x: * Virtual Infrastructure Client (VI Client, or VIC), client software that lets you connect to and manage ESX Server hosts directly, or through a VirtualCenter Server host; VirtualCenter Server 1.x: * VirtualCenter Client (VC Client), client software that lets you connect to and manage ESX Server 2.x hosts through a VirtualCenter Server host (1.x version). CVE Information: <http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-5990> CVE-2006-5990 ADDITIONAL INFORMATION The information has been provided by vmware. ======================================== This bulletin is sent to members of the SecuriTeam mailing list. To unsubscribe from the list, send mail with an empty subject line and body to: list-unsubscribe@securiteam.com In order to subscribe to the mailing list, simply forward this email to: list-subscribe@securiteam.com ==================== ==================== DISCLAIMER: The information in this bulletin is provided "AS IS" without warranty of any kind. In no event shall we be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages.
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [NT] Qbik WinGate Compressed Name Pointer DoS, SecuriTeam |
|---|---|
| Next by Date: | [UNIX] Horde Kronolith Arbitrary Local File Inclusion Vulnerability, SecuriTeam |
| Previous by Thread: | [NT] Qbik WinGate Compressed Name Pointer DoS, SecuriTeam |
| Next by Thread: | [UNIX] Horde Kronolith Arbitrary Local File Inclusion Vulnerability, SecuriTeam |
| Indexes: | [Date] [Thread] [Top] [All Lists] |