## Summary
The RC4 âBar Mitzvahâ Attack for SSL/TLS affects the IBM® FlashSystem⢠840 and IBM FlashSystem 900.
## Vulnerability Details
**CVEID:** [_CVE-2015-2808_]()
**DESCRIPTION:** The RC4 algorithm, as used in the TLS protocol and SSL protocol, could allow a remote attacker to obtain sensitive information. An attacker could exploit this vulnerability to remotely expose account credentials without requiring an active man-in-the-middle session. Successful exploitation could allow an attacker to retrieve credit card data or other sensitive information. This vulnerability is commonly referred to as “Bar Mitzvah Attack”.
CVSS Base Score: 5
CVSS Temporal Score: See [_https://exchange.xforce.ibmcloud.com/vulnerabilities/101851_]() for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:L/Au:N/C:P/I:N/A:N)
## Affected Products and Versions
_FlashSystem 840 including machine type and models (MTMs) for all available code levels._ MTMs affected include 9840-AE1 and 9843-AE1.
_FlashSystem 900 including machine type and models (MTMs) for all available code levels._ MTMs affected include 9840-AE2 and 9843-AE2.
## Remediation/Fixes
_FS840 & FS900 MTMs_
| _VRMF_| _APAR_| _Remediation/First Fix_
—|—|—|—
**FlashSystem ****840 MTM: **
9840-AE1 &
9843-AE1
**FlashSystem 900 MTMs:**
9840-AE2 &
9843-AE2| _A code fix is now available, the VRMF of this code level is 1.3.0.2 (or later)_| _ __N/A_| _No workarounds or mitigations, other than applying this code fix, are known for this vulnerability_
1.3.0.2 is available @ IBMâs Fix Central **: **[**_840 fixes, download 1.3.0.2 or later_**]()*
1.3.0.2 is available @ IBMâs Fix Central **: **[**_900 fixes, download 1.3.0.2 or later_**]()*
* This vulnerability had been previously fixed on the FlashSystem 840 and 900 for other ports, but was reintroduced in the code level 1.2.1.4 on the port opened to allow REST API control. FlashSystem 840 and 900 systems running code levels prior to 1.3.0.2, but at 1.2.1.4 or 1.2.1.7, only have this vulnerability on the port used exclusively by the REST API.
## Workarounds and Mitigations
None
References
Back to Main