CVE-2019-19835: SSRF
Published 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.
Affected Software
22 affected components
Ruckuswireless Unleashed<200.7.10.202.94
Ruckuswireless C110
Ruckuswireless E510
Ruckuswireless H320
Ruckuswireless H510
Ruckuswireless M510
Ruckuswireless R310
Ruckuswireless R320
Ruckuswireless R510
Ruckuswireless R610
Ruckuswireless R710
Ruckuswireless R720
Ruckuswireless T310
Ruckuswireless T610
Ruckuswireless T710
Ruckuswireless Zonedirector 1200 Firmware<9.10.2.0.84
Ruckuswireless Zonedirector 1200 Firmware>=9.12.0<9.12.3.0.136
Ruckuswireless Zonedirector 1200 Firmware>=9.13.0<10.0.1.0.90
Ruckuswireless Zonedirector 1200 Firmware>=10.1.0<10.1.2.0.275
Ruckuswireless Zonedirector 1200 Firmware>=10.2.0<10.2.1.0.147
Ruckuswireless Zonedirector 1200 Firmware>=10.3.0<10.3.1.0.21
Ruckuswireless Zonedirector 1200
Event History
Jan 23, 2020
CVE Published
via MITRE·12:44 PM
Data Sourced
via MITRE·12:44 PM
Description
Frequently Asked Questions
1
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.
2
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.
3
Which devices are affected by CVE-2019-19835?
CVE-2019-19835 affects Ruckus Wireless Unleashed versions prior to 200.7.10.202.94.
4
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.
5
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.