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.
Details: The GNU C library (glibc) had these vulnerabilities: CVE-2015-7547: a buffer overflow in client DNS lookups (getaddrinfo) that might allow malicious client connections from networks with malicious DNS servers to cause crashes or other harmful effects in server software to which these clients connect. This might affect servers (for example, SSH) that do DNS lookups on clients connecting to them. Malicious client connections from networks with malicious DNS servers can create the overflow conditions. CVE-2015-5229: the calloc() function might return a pointer to memory that is not filled with zero bytes. Fix: We have upgraded glibc to a version that fixes CVE-2015-7547 and CVE-2015-5229. Recommendation: Upgrade the software to a version with this fix. If this is not possible, avoid placing appliances on networks exposed to untrusted DNS clients.