# CVE-2018-21122: Denial of service in n/a

> Attackers can cause a denial of service on specific NETGEAR managed switches by exploiting improper input validation.

- **Severity:** Medium 6.5 (`CVSS:3.0/AC:L/AV:A/A:H/C:N/I:N/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Apr 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7cg3-666j-3r3x

## What is CVE-2018-21122?

CVE-2018-21122 is a medium-severity denial of service vulnerability in n/a, published on 22 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Certain NETGEAR devices are affected by denial of service. This affects GS110EMX before 1.0.0.9, GS810EMX before 1.0.0.5, XS512EM before 1.0.0.6, and XS724EM before 1.0.0.6.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-21122?

It affects 4 products.


Products: Netgear Gs110emx Firmware, Netgear Gs810emx Firmware, Netgear Xs512em Firmware, Netgear Xs724em Firmware.

## How do I fix CVE-2018-21122?

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

## Is CVE-2018-21122 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-26921](https://insights.sbomify.com/CVE-2020-26921/): Auth bypass in n/a (high 8.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-21122 and fix it if it is affected.

What it is: CVE-2018-21122 is a medium-severity denial of service vulnerability in n/a, published on 22 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-21122 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-2018-21122/ (Markdown: https://insights.sbomify.com/CVE-2018-21122/index.md)
```

## Sources

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

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