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.

Apache httpd less than 2.4.27 has vulnerabilities CVE-2017-9788 and CVE-2017-9789. (Bug #286625)

Products:
SteelHead (Appliance), SteelHead Interceptor, SteelCentral Controller for SteelHead (Central Management Console)
Fixed in Version:
steelhead 9.1.5c, steelhead 9.6.1, steelhead 9.2.3, steelhead 9.7.0, cmc 9.7.0, interceptor 7.0.0
Last Modified:
2018-05-17
Summary
DETAILS:

CVE-2017-9789:

When under stress, closing many connections, the HTTP/2 handling code in Apache httpd 2.4.26 would sometimes access memory after it has been freed, resulting in potentially erratic behavior.

CVE-2017-9788:

The value placeholder in [Proxy-]Authorization headers of type 'Digest' was not initialized or reset before or between successive key=value assignments. by mod_auth_digest.

Providing an initial key with no '=' assignment could reflect the stale value of uninitialized pool memory used by the prior request, leading to leakage of potentially confidential information, and a segfault. 

FIX:

Upgraded to Apache httpd 2.4.27.

RECOMMENDATION:

Upgrade to a software version with the fix.