Panel access and SSRF via login CSRF
Published May 5, 2020 · Updated Aug 4, 2024
Cross-site request forgery in login.asp on Ruckus R500 3.4.2.0.384 allows remote attackers to access its panel or trigger SSRF. The public record identifies login.asp as the vulnerable locus but does not disclose which request validation or anti-CSRF control is absent. Exploitation requires user interaction with a crafted request, and the documented consequence is limited to panel access or server-side requests.
Summary
What happened
Cross-site request forgery in login.asp on Ruckus R500 3.4.2.0.384 allows remote attackers to access its panel or trigger SSRF. The public record identifies login.asp as the vulnerable locus but does not disclose which request validation or anti-CSRF control is absent. Exploitation requires user interaction with a crafted request, and the documented consequence is limited to panel access or server-side requests.
The record
- CVE
- CVE-2020-7983
- Published
- May 5, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-352, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 5, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo