high
7.5
CWE
918
Advisory Published
Updated

CVE-2019-19835: SSRF

First published: Thu Jan 23 2020(Updated: )

SSRF in AjaxRestrictedCmdStat in zap in Ruckus Wireless Unleashed through 200.7.10.102.64 allows a remote denial of service via the server attribute to the tools/_rcmdstat.jsp URI.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
Ruckus Wireless Unleashed<200.7.10.202.94
Ruckus Wireless C110
Ruckus Wireless E510
Ruckus Wireless H320
Ruckus Wireless H510
Ruckus Wireless M510
Ruckus Wireless R310
Ruckus Wireless R320
Ruckus Wireless R510
Ruckus Wireless R610
Ruckus Wireless R710
Ruckus Wireless R720
Ruckus Wireless T310
Ruckus Wireless T610
Ruckus Wireless T710
Ruckus Wireless ZoneDirector 1200 Firmware<9.10.2.0.84
Ruckus Wireless ZoneDirector 1200 Firmware>=9.12.0<9.12.3.0.136
Ruckus Wireless ZoneDirector 1200 Firmware>=9.13.0<10.0.1.0.90
Ruckus Wireless ZoneDirector 1200 Firmware>=10.1.0<10.1.2.0.275
Ruckus Wireless ZoneDirector 1200 Firmware>=10.2.0<10.2.1.0.147
Ruckus Wireless ZoneDirector 1200 Firmware>=10.3.0<10.3.1.0.21
Ruckus Wireless ZoneDirector 1200

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2019-19835?

    CVE-2019-19835 has been classified as high severity due to its potential for remote denial of service attacks.

  • How do I fix CVE-2019-19835?

    To fix CVE-2019-19835, update your Ruckus Wireless Unleashed firmware to version 200.7.10.202.94 or later.

  • Which devices are affected by CVE-2019-19835?

    CVE-2019-19835 affects Ruckus Wireless Unleashed versions prior to 200.7.10.202.94.

  • Can I still use my vulnerable Ruckus device after CVE-2019-19835 is identified?

    Using a vulnerable Ruckus device after CVE-2019-19835 is identified poses significant risks, and it is recommended to apply the necessary updates immediately.

  • Is there a workaround for CVE-2019-19835?

    There is no known workaround for CVE-2019-19835; updating the firmware is the only effective mitigation.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203