# CVE-2020-7983: A CSRF issue in login.asp on Ruckus R500 3.4.2.0.384 devices allows remote attackers to access the panel or conduct SSRF attacks.


- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 5 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-m82h-9vwq-8x29

## What is CVE-2020-7983?

CVE-2020-7983 is a high-severity vulnerability in n/a, published on 5 May 2020. 

### Official description

A CSRF issue in login.asp on Ruckus R500 3.4.2.0.384 devices allows remote attackers to access the panel or conduct SSRF attacks.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2020-7983?

It affects 1 product.


Products: Commscope Ruckus Zoneflex R500 Firmware.

## How do I fix CVE-2020-7983?

No fix has been published for CVE-2020-7983 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-7983 being exploited?

There is no known exploitation of CVE-2020-7983 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2020-8830](https://insights.sbomify.com/CVE-2020-8830/): Server-side request forgery in n/a (high 8.8)
- [CVE-2020-8033](https://insights.sbomify.com/CVE-2020-8033/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-7983 and fix it if it is affected.

What it is: CVE-2020-7983 is a high-severity vulnerability in n/a, published on 5 May 2020. 
Exploitation: There is no known exploitation of CVE-2020-7983 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-7983/ (Markdown: https://insights.sbomify.com/CVE-2020-7983/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-7983
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-7983
- OSV: https://osv.dev/vulnerability/CVE-2020-7983

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-7983/
Summaries are generated and may contain mistakes; the official description above is the record.