# CVE-2018-21163: Memory corruption in n/a

> Authenticated attackers can trigger a stack-based buffer overflow in NETGEAR routers to execute arbitrary code or escalate privileges.

- **Severity:** Medium 6.8 (`CVSS:3.0/AC:L/AV:A/A:H/C:H/I:H/PR:H/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Apr 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j5rp-qhhj-8vw3

## What is CVE-2018-21163?

CVE-2018-21163 is a medium-severity memory corruption vulnerability in Netgear Ex6200 Firmware, published on 23 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 a stack-based buffer overflow by an authenticated user. This affects DGN2200Bv4 before 1.0.0.102, DGN2200v4 before 1.0.0.102, EX3700 before 1.0.0.70, EX3800 before 1.0.0.70, EX6000 before 1.0.0.30, EX6100 before 1.0.2.22, EX6120 before 1.0.0.40, EX6130 before 1.0.0.22, EX6150 before 1.0.0.38, EX6200 before 1.0.3.86, EX7000 before 1.0.0.64, R6300v2 before 1.0.4.22, R6900P before 1.3.0.18, R7000P before 1.3.0.18, R7300DST before 1.0.0.62, R7900P before 1.3.0.10, R8000 before 1.0.4.12, R8000P before 1.3.0.10, WN2500RPv2 before 1.0.1.52, and WNDR3400v3 before 1.0.1.18.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 20 products.


Products: Netgear Dgn2200 Firmware, Netgear Dgn2200b Firmware, Netgear Ex3700 Firmware, Netgear Ex3800 Firmware, Netgear Ex6000 Firmware, Netgear Ex6100 Firmware, Netgear Ex6120 Firmware, Netgear Ex6130 Firmware, Netgear Ex6150 Firmware, Netgear Ex6200 Firmware, Netgear Ex7000 Firmware, Netgear R6300 Firmware, Netgear R6900p Firmware, Netgear R7000p Firmware, Netgear R7300dst Firmware, Netgear R7900p Firmware, Netgear R8000 Firmware, Netgear R8000p Firmware, Netgear Wn2500rp Firmware, Netgear Wndr3400 Firmware.

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

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

## Is CVE-2018-21163 being exploited?

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

## Other vulnerabilities in Netgear Ex6200 Firmware

- [CVE-2017-6077](https://insights.sbomify.com/CVE-2017-6077/): NETGEAR DGN2200 Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-17373](https://insights.sbomify.com/CVE-2019-17373/): Auth bypass in n/a (critical 9.8)
- [CVE-2016-5649](https://insights.sbomify.com/CVE-2016-5649/): Netgear DGN2200 and DGND3700 disclose the administrator password (critical 9.8)
- [CVE-2024-57046](https://insights.sbomify.com/CVE-2024-57046/): Auth bypass in n/a (high 8.8)
- [CVE-2017-18755](https://insights.sbomify.com/CVE-2017-18755/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-21163 is a medium-severity memory corruption vulnerability in Netgear Ex6200 Firmware, published on 23 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-21163 in the wild and no public exploit code.

Affected product: Netgear Ex6200 Firmware. 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-21163/ (Markdown: https://insights.sbomify.com/CVE-2018-21163/index.md)
```

## Sources

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

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