<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>VMware Communities: Message List - SSL Server support weak encryption</title>
    <link>http://communities.vmware.com/community/vmtn/general/security?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Tue, 11 Aug 2009 16:02:40 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-08-11T16:02:40Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: SSL Server support weak encryption</title>
      <link>http://communities.vmware.com/message/1334569?tstart=0#1334569</link>
      <description>Hello,&lt;br /&gt;
&lt;br /&gt;
You could change it in these files.... Not sure what would happen but do not think it is an issue.....&lt;br /&gt;
&lt;br /&gt;
/usr/lib/vmware/webAccess/tomcat/*/conf/server.xml&lt;br /&gt;
&lt;br /&gt;
However, not everything uses tomcat either so there are other concerns as well. This just fixes it for webAccess which includes anything using the VI-SDK, etc.&lt;br /&gt;
&lt;br /&gt;
&lt;br&gt;Best regards, &lt;br /&gt;
Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009, &lt;a class="jive-link-external" href="http://www.virtualizationpractice.com"&gt;Virtualization Practice Analyst&lt;/a&gt;&lt;br&gt;Now Available: &lt;a class="jive-link-external" href="http://www.astroarch.com/wiki/index.php/VMware_Virtual_Infrastructure_Security"&gt;'VMware vSphere(TM) and Virtual Infrastructure Security: Securing the Virtual Environment'&lt;/a&gt;&lt;br&gt;Also available &lt;a class="jive-link-external" href="http://www.astroarch.com/wiki/index.php/VMWare_ESX_Server_in_the_Enterprise"&gt;'VMWare ESX Server in the Enterprise'&lt;/a&gt;&lt;br&gt;&lt;a class="jive-link-external" href="http://www.astroarch.com/wiki/index.php/Blog_Roll"&gt;SearchVMware Pro&lt;/a&gt;|&lt;a class="jive-link-external" href="http://www.astroarch.com/blog"&gt;Blue Gears&lt;/a&gt;|&lt;a class="jive-link-external" href="http://www.astroarch.com/wiki/index.php/Top_Virtualization_Security_Links"&gt;Top Virtualization Security Links&lt;/a&gt;|&lt;a class="jive-link-external" href="http://www.astroarch.com/wiki/index.php/Virtualization_Security_Round_Table_Podcast"&gt;Virtualization Security Round Table Podcast&lt;/a&gt;</description>
      <pubDate>Tue, 11 Aug 2009 16:02:40 GMT</pubDate>
      <author>Texiwill</author>
      <guid>http://communities.vmware.com/message/1334569?tstart=0#1334569</guid>
      <dc:date>2009-08-11T16:02:40Z</dc:date>
      <clearspace:dateToText>3 months, 2 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: SSL Server support weak encryption</title>
      <link>http://communities.vmware.com/message/1333748?tstart=0#1333748</link>
      <description>&lt;br /&gt;
Openssl recompile is not needed to disable weak ciphers. This is usally a server side option/configuration of the application using openssl.&lt;br /&gt;
&lt;p /&gt;
For example, in Apache/mod_ssl this is controlled by SSLCipherSuite parameter, in Tomcat, this is controlled by ciphers parameter in the server.xml config file, ....&lt;br /&gt;
&lt;p /&gt;
For VMware there seems to be no way to configure this but this is currently addressed according the rrandel previous post.</description>
      <pubDate>Mon, 10 Aug 2009 18:54:33 GMT</pubDate>
      <author>glopglop</author>
      <guid>http://communities.vmware.com/message/1333748?tstart=0#1333748</guid>
      <dc:date>2009-08-10T18:54:33Z</dc:date>
      <clearspace:dateToText>3 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: SSL Server support weak encryption</title>
      <link>http://communities.vmware.com/message/1333746?tstart=0#1333746</link>
      <description>&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
I tend to agree with you that the risk is minimal but some security officers/auditors like to have "clean" scan results. &lt;br /&gt;
&lt;p /&gt;
It is good to know that this is being addressed as this will avoid lenghty discussions with auditors in the future.</description>
      <pubDate>Mon, 10 Aug 2009 18:45:58 GMT</pubDate>
      <author>glopglop</author>
      <guid>http://communities.vmware.com/message/1333746?tstart=0#1333746</guid>
      <dc:date>2009-08-10T18:45:58Z</dc:date>
      <clearspace:dateToText>3 months, 2 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: SSL Server support weak encryption</title>
      <link>http://communities.vmware.com/message/1333503?tstart=0#1333503</link>
      <description>Hello,&lt;br /&gt;
&lt;br /&gt;
The only way I know to do this would be to recompile openSSL without those ciphers. I am glad the test is more than just looking at version numbers. But as Rob stated, your management network should be protected with a well defined set of tools connecting to it.&lt;br /&gt;
&lt;br /&gt;
&lt;br&gt;Best regards, &lt;br /&gt;
Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009, &lt;a class="jive-link-external" href="http://www.virtualizationpractice.com"&gt;Virtualization Practice Analyst&lt;/a&gt;&lt;br&gt;Now Available: &lt;a class="jive-link-external" href="http://www.astroarch.com/wiki/index.php/VMware_Virtual_Infrastructure_Security"&gt;'VMware vSphere(TM) and Virtual Infrastructure Security: Securing the Virtual Environment'&lt;/a&gt;&lt;br&gt;Also available &lt;a class="jive-link-external" href="http://www.astroarch.com/wiki/index.php/VMWare_ESX_Server_in_the_Enterprise"&gt;'VMWare ESX Server in the Enterprise'&lt;/a&gt;&lt;br&gt;&lt;a class="jive-link-external" href="http://www.astroarch.com/wiki/index.php/Blog_Roll"&gt;SearchVMware Pro&lt;/a&gt;|&lt;a class="jive-link-external" href="http://www.astroarch.com/blog"&gt;Blue Gears&lt;/a&gt;|&lt;a class="jive-link-external" href="http://www.astroarch.com/wiki/index.php/Top_Virtualization_Security_Links"&gt;Top Virtualization Security Links&lt;/a&gt;|&lt;a class="jive-link-external" href="http://www.astroarch.com/wiki/index.php/Virtualization_Security_Round_Table_Podcast"&gt;Virtualization Security Round Table Podcast&lt;/a&gt;</description>
      <pubDate>Mon, 10 Aug 2009 15:09:34 GMT</pubDate>
      <author>Texiwill</author>
      <guid>http://communities.vmware.com/message/1333503?tstart=0#1333503</guid>
      <dc:date>2009-08-10T15:09:34Z</dc:date>
      <clearspace:dateToText>3 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Re: SSL Server support weak encryption</title>
      <link>http://communities.vmware.com/message/1333472?tstart=0#1333472</link>
      <description>It is the case that these weaker ciphers are currently supported.  This is being addressed, but IMHO the risk is VERY minimal.  The fact is that the only way this risk could be realized is if one of your administrators used a browser that only supported the weak ciphers.  The VIC, nor do most modern browsers support weak ciphers.  From my perspective, this is more of a concern for a public facing website to allow this, since you don't necessarily know what the "users" of the website are using for their browser.  In a corporate environment, you should be able to control what browser your administrators are using which will completely mitigate this risk.</description>
      <pubDate>Mon, 10 Aug 2009 14:51:14 GMT</pubDate>
      <author>rrandell</author>
      <guid>http://communities.vmware.com/message/1333472?tstart=0#1333472</guid>
      <dc:date>2009-08-10T14:51:14Z</dc:date>
      <clearspace:dateToText>3 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Re: SSL Server support weak encryption</title>
      <link>http://communities.vmware.com/message/1333150?tstart=0#1333150</link>
      <description>&lt;br /&gt;
SSL Server Weak encryption is not done by checking openssl version but by simply trying to open a connection using a weak cipher.&lt;br /&gt;
&lt;p /&gt;
For example on ESX 3.5, the following weak ciphers are detected (56 bit encryption).&lt;br /&gt;
&lt;br /&gt;
&lt;table class="jive-wiki-table"&gt;
&lt;tr&gt;
&lt;td&gt;CIPHER&lt;/td&gt;
&lt;td&gt;KEY-EXCHANGE&lt;/td&gt;
&lt;td&gt;AUTHENTICATION&lt;/td&gt;
&lt;td&gt;MAC&lt;/td&gt;
&lt;td&gt;ENCRYPTION(KEY-STRENGTH)&lt;/td&gt;
&lt;td&gt;GRADE&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;SSLv3 WEAK CIPHERS&lt;/td&gt;
&lt;td&gt;&amp;nbsp;&lt;/td&gt;
&lt;td&gt;&amp;nbsp;&lt;/td&gt;
&lt;td&gt;&amp;nbsp;&lt;/td&gt;
&lt;td&gt;&amp;nbsp;&lt;/td&gt;
&lt;td&gt;&amp;nbsp;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;EXP1024-RC4-SHA&lt;/td&gt;
&lt;td&gt;RSA(1024)&lt;/td&gt;
&lt;td&gt;RSA&lt;/td&gt;
&lt;td&gt;SHA1&lt;/td&gt;
&lt;td&gt;RC4(56)&lt;/td&gt;
&lt;td&gt;LOW&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;EXP1024-DES-CBC-SHA&lt;/td&gt;
&lt;td&gt;RSA(1024)&lt;/td&gt;
&lt;td&gt;RSA&lt;/td&gt;
&lt;td&gt;SHA1&lt;/td&gt;
&lt;td&gt;DES(56)&lt;/td&gt;
&lt;td&gt;LOW&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;DES-CBC-SHA&lt;/td&gt;
&lt;td&gt;RSA&lt;/td&gt;
&lt;td&gt;RSA&lt;/td&gt;
&lt;td&gt;SHA1&lt;/td&gt;
&lt;td&gt;DES(56)&lt;/td&gt;
&lt;td&gt;LOW&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;TLSv1 WEAK CIPHERS&lt;/td&gt;
&lt;td&gt;&amp;nbsp;&lt;/td&gt;
&lt;td&gt;&amp;nbsp;&lt;/td&gt;
&lt;td&gt;&amp;nbsp;&lt;/td&gt;
&lt;td&gt;&amp;nbsp;&lt;/td&gt;
&lt;td&gt;&amp;nbsp;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;EXP1024-RC4-SHA&lt;/td&gt;
&lt;td&gt;RSA(1024)&lt;/td&gt;
&lt;td&gt;RSA&lt;/td&gt;
&lt;td&gt;SHA1&lt;/td&gt;
&lt;td&gt;RC4(56)&lt;/td&gt;
&lt;td&gt;LOW&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;EXP1024-DES-CBC-SHA&lt;/td&gt;
&lt;td&gt;RSA(1024)&lt;/td&gt;
&lt;td&gt;RSA&lt;/td&gt;
&lt;td&gt;SHA1&lt;/td&gt;
&lt;td&gt;DES(56)&lt;/td&gt;
&lt;td&gt;LOW&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;DES-CBC-SHA&lt;/td&gt;
&lt;td&gt;RSA&lt;/td&gt;
&lt;td&gt;RSA&lt;/td&gt;
&lt;td&gt;SHA1&lt;/td&gt;
&lt;td&gt;DES(56)&lt;/td&gt;
&lt;td&gt;LOW&lt;/td&gt;
&lt;/tr&gt;
&lt;/table&gt;
&lt;br clear="left" /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
You can test it by running: &lt;br /&gt;
&lt;p /&gt;
 openssl  s_client -connect &amp;lt;hostname of ESX console&amp;gt;:443 -cipher DES-CBC-SHA&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
If you are getting an answer, then the weak cipher is supported.&lt;br /&gt;
&lt;p /&gt;
So the question remains open. Is there a way to we enforce only strong cipher.</description>
      <pubDate>Mon, 10 Aug 2009 07:50:30 GMT</pubDate>
      <author>glopglop</author>
      <guid>http://communities.vmware.com/message/1333150?tstart=0#1333150</guid>
      <dc:date>2009-08-10T07:50:30Z</dc:date>
      <clearspace:dateToText>3 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>Re: SSL Server support weak encryption</title>
      <link>http://communities.vmware.com/message/1300259?tstart=0#1300259</link>
      <description>Hello,&lt;br /&gt;
&lt;br /&gt;
Moved to the Security Forum.&lt;br /&gt;
&lt;br /&gt;
Welcome to the forums. The big issue about this question, and it actually comes up a lot, is how the 'tool' you are using is finding this vulnerability. I imagine it is looking at the version of OpenSSL installed on the host and not actually trying to run an exploit. If it is looking at the version # then it is a false positive, as like RedHat, VMware backports changes into OpenSSL without changing the version number of the package.&lt;br /&gt;
&lt;br /&gt;
If it is testing the certificates in use, then replace the self-signed certificates with your own signed certificates.&lt;br /&gt;
&lt;br /&gt;
&lt;br&gt;Best regards, &lt;br /&gt;
Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009, &lt;a class="jive-link-external" href="http://www.virtualizationpractice.com"&gt;Virtualization Practice Analyst&lt;/a&gt;&lt;br&gt;Now Available: &lt;a class="jive-link-external" href="http://www.astroarch.com/wiki/index.php/VMware_Virtual_Infrastructure_Security"&gt;'VMware vSphere(TM) and Virtual Infrastructure Security: Securing the Virtual Environment'&lt;/a&gt;&lt;br&gt;Also available &lt;a class="jive-link-external" href="http://www.astroarch.com/wiki/index.php/VMWare_ESX_Server_in_the_Enterprise"&gt;'VMWare ESX Server in the Enterprise'&lt;/a&gt;&lt;br&gt;&lt;a class="jive-link-external" href="http://www.astroarch.com/wiki/index.php/Blog_Roll"&gt;SearchVMware Pro&lt;/a&gt;|&lt;a class="jive-link-external" href="http://www.astroarch.com/blog"&gt;Blue Gears&lt;/a&gt;|&lt;a class="jive-link-external" href="http://www.astroarch.com/wiki/index.php/Top_Virtualization_Security_Links"&gt;Top Virtualization Security Links&lt;/a&gt;|&lt;a class="jive-link-external" href="http://www.astroarch.com/wiki/index.php/Virtualization_Security_Round_Table_Podcast"&gt;Virtualization Security Round Table Podcast&lt;/a&gt;</description>
      <pubDate>Wed, 01 Jul 2009 17:33:37 GMT</pubDate>
      <author>Texiwill</author>
      <guid>http://communities.vmware.com/message/1300259?tstart=0#1300259</guid>
      <dc:date>2009-07-01T17:33:37Z</dc:date>
      <clearspace:dateToText>4 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>SSL Server support weak encryption</title>
      <link>http://communities.vmware.com/message/1299800?tstart=0#1299800</link>
      <description>&lt;br /&gt;
Completed a vulnerability study on our ESX 3.5 environment and its high lighted (SSL (Sercure Socket Layer) Server support weak encryption keys, which are defined as encryption keys with lengths of less 128 bits. Message encypted with weak encryption keys are relatively easy for an unauthorized user decrpt) on port 443.&lt;br /&gt;
&lt;p /&gt;
 I have looked at the VMware Secuirty Hardening document and it say that it Must always be available.&lt;br /&gt;
&lt;p /&gt;
 Should this be left allow, or is there anything I can do to correct this?&lt;br /&gt;
&lt;p /&gt;
 Thanks</description>
      <pubDate>Wed, 01 Jul 2009 09:30:56 GMT</pubDate>
      <author>MAD1969</author>
      <guid>http://communities.vmware.com/message/1299800?tstart=0#1299800</guid>
      <dc:date>2009-07-01T09:30:56Z</dc:date>
      <clearspace:dateToText>4 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>7</clearspace:replyCount>
    </item>
  </channel>
</rss>

