Report a potential issue:

The Ruckus Security Incident Response Policy

View customer-only security bulletins

Ruckus response to the WPA2 (KRACK) vulnerability:
Ruckus Wireless Support Resource Center

The Ruckus Product Security Team is responsible for researching, analyzing and responding to security incident reports related to Ruckus products. This team is the first point of contact for all security incident reports and works directly with Ruckus customers, security researchers, government organizations, consultants, industry security organizations, and other vendors to identify security issues with Ruckus products. This team is also responsible for publishing security advisories and communicating with outside entities regarding mitigation steps for addressing particular security issues with Ruckus products.

Reporting a Security Issue to Ruckus

Ruckus encourages individuals and organizations to report all Ruckus-related product related vulnerabilities and security issues directly to Ruckus via our email alias:

A link to the Ruckus Security Incident Response Policy is available here.

Please provide a detailed description of the issue along with sufficient information to reasonably enable Ruckus to reproduce the issue. Please also include a technical contact, list of Ruckus products affected and any other helpful information such as logs and console messages etc.

If you are a currently experiencing a network outage or need help configuring a security feature, please contact Ruckus via any of the contact methods listed on the Support Contact page.

Security Bulletins

IDTitleVersionRelease DateEdit DateFAQ
20190815TCP SACK Panic - Kernel Vulnerability (CVE-2019-11477, CVE-2019-11478, CVE-2019-11479)1.0August 15, 2019August 15, 2019
BSA-2014-002CVE-2014-3566 - OpenSSL N/AMarch 10, 2015April 7, 2017
BSA-2015-001GNU C Library “GHOST” Vulnerability (CVE-2015-0235) Assessment for Brocade N/AFebruary 13, 2015May 11, 2016
BSA-2015-002CVE-2014-9296 - NTP N/AMarch 19, 2015May 11, 2016
BSA-2015-003CVE-2014-3569 - OpenSSL CVE-2014-3570 - OpenSSL CVE-2014-3571 - OpenSSL CVE-2014-3572 - OpenSSL CVE-2014-8275 - OpenSSL CVE-2015-0204 - OpenSSL CVE-2015-0205 - OpenSSL CVE-2015-0206 - OpenSSL N/AApril 24, 2015March 23, 2017
BSA-2017-201CVE-2016-8610 N/AMarch 31, 2017March 31, 2017
BSA-2017-204CVE-2016-3961 N/AMarch 31, 2017March 31, 2017
BSA-2017-205CVE-2016-7054 N/AMarch 31, 2017March 31, 2017
BSA-2017-206CVE-2016-7053 N/AMarch 31, 2017March 31, 2017
BSA-2017-207CVE-2016-7055 N/AMarch 31, 2017March 31, 2017