# CVE-2021-36630: Denial of service in n/a

> Remote attackers can cause denial of service against Ruckus SmartZone controllers via crafted requests exploiting the eAut module.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jan 2023
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-282c-5v9j-jrrc

## What is CVE-2021-36630?

CVE-2021-36630 is a high-severity denial of service vulnerability in n/a, published on 18 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

DDOS reflection amplification vulnerability in eAut module of Ruckus Wireless SmartZone controller that allows remote attackers to perform DOS attacks via crafted request.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2021-36630?

It affects 4 products.


Products: Ruckuswireless Sz-100 Firmware, Ruckuswireless Sz-144 Firmware, Ruckuswireless Sz-300 Firmware, Ruckuswireless Vsz Firmware.

## How do I fix CVE-2021-36630?

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

## Is CVE-2021-36630 being exploited?

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

Public exploit code:

- https://github.com/lixiang957/CVE-2021-36630 (github_poc): https://github.com/lixiang957/CVE-2021-36630

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-36630 and fix it if it is affected.

What it is: CVE-2021-36630 is a high-severity denial of service vulnerability in n/a, published on 18 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-36630 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-2021-36630/ (Markdown: https://insights.sbomify.com/CVE-2021-36630/index.md)
```

## Sources

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

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