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-3192: Apache HTTP server Byterange filter Denial of Service (Bug #103546)

Product

SteelHead Interceptor

Fixed in Version:

RBT IC 3.0.0c, interceptor 3.0.0c

Last Modified:

2015-05-13

Summary

Details:

The byterange filter in the Apache HTTP Server 1.3.x, 2.0.x through 2.0.64, and 2.2.x through 2.2.19 allows remote attackers to cause a denial of service (memory and CPU consumption) via a Range header that expresses multiple overlapping ranges, as exploited in the wild in August 2011, a different vulnerability than CVE-2007-0086.

Fix:

In Apache httpd configuration, mod_headers are used to disable Range and Request-Range headers for CVE-2011-3192 denial-of-service attack. 

Recommendation:

Upgrade to patched version if applicable. More information on the suitability of this mitigation approach can be found the the corresponding Apache security advisory at http://httpd.apache.org/security/CVE-2011-3192.txt.

Feedback