Security Finder

You can use the Security Finder to search for security issues and their impact on Riverbed products. This page is continuously updated, displaying the most current public security issues first. The search box can be used to look up records by specific CVE numbers or relevant search word, e.g. Apache, 8.5.0, Workaround. For additional search tips, refer to article S16165. Security issues listed here are categorized into three groups: fixed, workaround recommended and not applicable.

For general security topics, security best practices and other security related topics, try performing a general search.

BETA FEATURE: This feature is currently under development and is considered Beta Software. We are still enhancing the features and results so please exercise caution when interpreting and implementing the results. If you have any questions, please open a case with Riverbed Support. If you have feedback for this tool, please send it to supportfeedback@riverbed.com.

Riverbed Technology is committed to protecting customers against vulnerabilities in our supported products. Vulnerabilities are addressed in accordance to the software support policy. https://support.riverbed.com/content/support/about_support/end_of_life_policy.html

For search tips, read article S16165.

CVE-2011-3389: HTTPS block-wise chosen-plaintext attack against SSL/TLS ("BEAST" attack) (Bug #94280)

Products:

SteelHead (Appliance), SteelHead Interceptor, SteelCentral Controller for SteelHead (Central Management Console)

Fixed in Version:

RBT CMC 6.5.2, RBT SH 6.5.4, RBT IC 3.0.0c, RBT SH 7.0.0, interceptor 3.0.0c

Last Modified:

2015-05-13

Summary

Details:

The SSL protocol encrypts data by using CBC mode with chained initialization vectors, which allows man-in-the-middle attackers to obtain plaintext HTTP headers via a blockwise chosen-boundary attack (BCBA) on an HTTPS session, in conjunction with JavaScript code that uses the HTML5 WebSocket API, the Java URLConnection API, or the Silverlight WebClient API, aka a "BEAST" attack.

Fix:

Disabling the default OpenSSL flag SSL_OP_DONT_INSERT_EMPTY_FRAGMENTS eliminates the condition under which this attack succeeds. We have disabled this flag in our OpenSSL configuration. Additionally, we have disabled SSLv2 completely, and all weak TLS ciphers.

Recommendation:

Upgrade to patched version if applicable.

Feedback