# CVE-2017-18837: Privilege escalation in n/a

> Attackers can escalate privileges on NETGEAR M4300 and M4200 series managed switches, requiring firmware upgrades to mitigate.

- **Severity:** High 7.8 (`CVSS:3.0/AC:L/AV:L/A:H/C:H/I:H/PR:L/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Apr 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-q2fx-gcj5-2r88

## What is CVE-2017-18837?

CVE-2017-18837 is a high-severity vulnerability in n/a, published on 20 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 vertical privilege escalation. This affects M4300-28G before 12.0.2.15, M4300-52G before 12.0.2.15, M4300-28G-POE+ before 12.0.2.15, M4300-52G-POE+ before 12.0.2.15, M4300-8X8F before 12.0.2.15, M4300-12X12F before 12.0.2.15, M4300-24X24F before 12.0.2.15, M4300-24X before 12.0.2.15, M4300-48X before 12.0.2.15, and M4200 before 12.0.2.15.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2017-18837?

It affects 10 products.


Products: Netgear M4200 Firmware, Netgear M4300-12x12f Firmware, Netgear M4300-24x24f Firmware, Netgear M4300-24x Firmware, Netgear M4300-28g-Poe\+ Firmware, Netgear M4300-28g Firmware, Netgear M4300-48x Firmware, Netgear M4300-52g-Poe\+ Firmware, Netgear M4300-52g Firmware, Netgear M4300-8x8f Firmware.

## How do I fix CVE-2017-18837?

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

## Is CVE-2017-18837 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-18822](https://insights.sbomify.com/CVE-2017-18822/): Privilege escalation in n/a (high 7.8)
- [CVE-2017-18826](https://insights.sbomify.com/CVE-2017-18826/): Privilege escalation in n/a (high 7.8)
- [CVE-2017-18829](https://insights.sbomify.com/CVE-2017-18829/): Privilege escalation in n/a (high 7.8)
- [CVE-2017-18830](https://insights.sbomify.com/CVE-2017-18830/): Privilege escalation in n/a (high 7.8)
- [CVE-2017-18831](https://insights.sbomify.com/CVE-2017-18831/): Cross-site scripting in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-18837 and fix it if it is affected.

What it is: CVE-2017-18837 is a high-severity vulnerability in n/a, published on 20 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-2017-18837 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-2017-18837/ (Markdown: https://insights.sbomify.com/CVE-2017-18837/index.md)
```

## Sources

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

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