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

Riverbed Technology is committed to protecting customers against vulnerabilities in our supported products. Vulnerabilities are addressed in accordance to the software support policy.

For search tips, read article S16165.

CVE-2018-1000005: libcurl contains an out bounds read in code handling HTTP/2 trailers. (Bug #296566)

SteelHead (Appliance), SteelHead Interceptor, SteelCentral Controller for SteelHead (Central Management Console)
Fixed in Version:
steelhead 9.7.1, steelhead 9.8.0, cmc 9.8.0, steelhead 9.6.3, steelhead 9.2.4, interceptor 7.1.0
Last Modified:


libcurl contains an out bounds read in code handling HTTP/2 trailers.

It was reported that reading an HTTP/2 trailer could mess up future trailers since the stored size was one byte less than required.

The problem is that the code that creates HTTP/1-like headers from the HTTP/2
trailer data once appended a string like ":" to the target buffer, while this
was recently changed to ": " (a space was added after the colon) but the
associated math wasn't updated correspondingly.

When accessed, the data is read out of bounds and causes either a crash or that
the (too large) data gets passed to the libcurl callback. This might lead to a
denial-of-service situation or an information disclosure if someone has a
service that echoes back or uses the trailers for something.

We are not aware of any exploit of this flaw.


curl might leak authentication data to third parties.

When asked to send custom headers in its HTTP requests, curl will send that set
of headers first to the host in the initial URL but also, if asked to follow
redirects and a 30X HTTP response code is returned to the host mentioned in
URL in the Location: response header value.

Sending the same set of headers to subsequest hosts is in particular a problem
for applications that pass on custom Authorization: headers, as this header
often contains privacy sensitive information or data that could allow others to
impersonate the curl-using client's request.

We are not aware of any exploit of this flaw.


Upgraded curl to 7.58.0.


Upgrade to a software version with the fix.