Security Bulletin: Vulnerabilities in SSL and TLS protocols affects SAN Volume Controller and Storwize Family (CVE-2011-3389)


## Summary Security Bulletin: Vulnerabilities in SSL and TLS protocols affects SAN Volume Controller and Storwize Family (CVE-2011-3389) ## Vulnerability Details ## Security Bulletin --- Summary --- SSL and TLS vulnerabilities were disclosed in September 2011. This vulnerability has been referred to as the “BEAST” attack. SSL protocol is used by SAN Volume Controller and Storwize Family. ## Vulnerability Details --- **CVE-ID**: [_CVE-2011-3389_](<https://vulners.com/cve/CVE-2011-3389>) **DESCRIPTION**: Multiple products could allow a remote attacker to obtain sensitive information, caused by a design error in the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols when using a Cipher-Block Chaining (CBC) based cryptographic algorithm. By persuading a victim to visit a Web site, a remote attacker could exploit this vulnerability using man-in-the-middle techniques to decrypt HTTPS sessions and obtain sensitive information. CVSS Base Score: 4.3 CVSS Temporal Score: See [**_http://xforce.iss.net/xforce/xfdb/70069_**](<http://xforce.iss.net/xforce/xfdb/70069>) for the current score CVSS Environmental Score*: Undefined CVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N) ## Affected Products and Versions --- IBM SAN Volume Controller Storwize V7000 for Lenovo Storwize V5000 for Lenovo Storwize V3700 for Lenovo Storwize V3500 for Lenovo All products are affected when running supported releases 1.1 to 7.3. Release 7.4 is not affected once the minimum SSL protocol level has been set (see below). ## Remediation/Fixes --- Lenovo recommends that you fix this vulnerability by upgrading affected versions of IBM SAN Volume Controller, Storwize V7000, V5000, V3700 and V3500 for Lenovo to the following code level or higher: [ _Latest SAN Volume Controller Code_](<http://www-01.ibm.com/support/docview.wss?rs=591&uid=ssg1S1001707>) [_Latest Storwize V7000 Code_](<http://www-01.ibm.com/support/docview.wss?uid=ssg1S1003705>) [_Latest Storwize V5000 Code_](<http://www-01.ibm.com/support/docview.wss?uid=ssg1S1004336>) [_Latest Storwize V3700 Code_](<http://www-01.ibm.com/support/docview.wss?uid=ssg1S1004172>) [_Latest Storwize V3500 Code_](<http://www-01.ibm.com/support/docview.wss?uid=ssg1S1004171>) Once you have upgraded the system you should use the CLI command “lssecurity” to determine the current minimum level of SSL protocol allowed. If it is less than level 3 (which allows only TLS 1.2 with ciphers exclusive to TLS 1.2) then modify it with CLI command “chsecurity”. This could cause systems connected to this system via SSL to stop working because they require upgrade or reconfiguration to allow them to use TLS 1.2 with exclusive ciphers. Upgrade those systems or use “chsecurity” again to reduce the minimum level this system uses until the connection works again. The system is vulnerable until its SSL protocol level is set to 3 using “chsecurity”. [ _SAN Volume Controller 7.4 Knowledge Center - lssecurity command_](<http://www-01.ibm.com/support/knowledgecenter/STPVGU_7.4.0/com.ibm.storage.svc.console.740.doc/svc_lssecurity.html?lang=en>) [ _SAN Volume Controller 7.4 Knowledge Centre - chsecurity command_](<http://www-01.ibm.com/support/knowledgecenter/STPVGU_7.4.0/com.ibm.storage.svc.console.740.doc/svc_chsecurity.html?lang=en>) Lenovo recommends that you review your entire environment to identify levels of SSL protocol being used. ## Workarounds and Mitigations --- Although Lenovo recommends that you install a level of code with a fix for this vulnerability, you can mitigate, although not eliminate, your risk until you have done so by ensuring that all users who have access to the system are authenticated by another security system such as a firewall. ##