Report a potential issue: [email protected]
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: [email protected].
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.
Ruckus highly recommends protecting the email communication with the PGP key below for encrypting any sensitive information sent to Ruckus.
To send the confidential information always use PGP Keys only. Please ask for the key info and keys by sending email to [email protected].
|ID||Title||Version||Release Date||Edit Date||FAQ|
|BSA-2017-265||CVE-2017-6074||N/A||May 2, 2017||October 13, 2017|
|BSA-2017-264||CVE-2017-3733||N/A||May 2, 2017||May 2, 2017|
|BSA-2017-260||CVE-2017-3732||N/A||May 2, 2017||May 2, 2017|
|BSA-2017-259||CVE-2017-3731||N/A||May 2, 2017||May 2, 2017|
|BSA-2017-258||CVE-2017-3730||N/A||May 2, 2017||May 2, 2017|
|BSA-2017-257||CVE-2015-8138||N/A||May 2, 2017||May 2, 2017|
|BSA-2017-255||CVE-2015-5600||N/A||May 2, 2017||May 2, 2017|
|BSA-2017-254||CVE-2013-4548||N/A||May 2, 2017||May 2, 2017|
|BSA-2017-253||CVE-2014-2532||N/A||May 2, 2017||September 8, 2017|
|BSA-2017-250||CVE-2017-5335||N/A||May 2, 2017||May 2, 2017|