# CVE-2023-38102: NETGEAR ProSAFE Network Management System createUser Missing Authorization Privilege Escalation Vulnerability

> Remote attackers can escalate privileges in NETGEAR ProSAFE NMS by bypassing authorization checks in the createUser function.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2024
- **Updated:** 18 Sep 2024
- **Also known as:** GHSA-mv86-4pvc-4wx9

## What is CVE-2023-38102?

CVE-2023-38102 is a high-severity missing authorization vulnerability in NETGEAR ProSAFE Network Management System, published on 3 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

NETGEAR ProSAFE Network Management System createUser Missing Authorization Privilege Escalation Vulnerability. This vulnerability allows remote attackers to escalate privileges on affected installations of NETGEAR ProSAFE Network Management System. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed.

The specific flaw exists within the createUser function. The issue results from the lack of authorization prior to allowing access to functionality. An attacker can leverage this vulnerability to escalate privileges to resources normally protected from the user. Was ZDI-CAN-19726.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2023-38102?

It affects 1 product.


Products: Netgear Prosafe Network Management System.

## How do I fix CVE-2023-38102?

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

## Is CVE-2023-38102 being exploited?

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

## Other vulnerabilities in NETGEAR ProSAFE Network Management System

- [CVE-2023-38096](https://insights.sbomify.com/CVE-2023-38096/): NETGEAR ProSAFE Network Management System MyHandlerInterceptor Authentication Bypass Vulnerability (critical 9.8)
- [CVE-2023-49693](https://insights.sbomify.com/CVE-2023-49693/): NETGEAR ProSAFE Network Management System RCE via Unprotected Access to Java Debug Wire Protocol (critical 9.8)
- [CVE-2021-27274](https://insights.sbomify.com/CVE-2021-27274/): File upload in ProSAFE Network Management System (critical 9.8)
- [CVE-2024-6813](https://insights.sbomify.com/CVE-2024-6813/): NETGEAR ProSAFE Network Management System getSortString SQL Injection Remote Code Execution Vulnerability (high 8.8)
- [CVE-2024-6814](https://insights.sbomify.com/CVE-2024-6814/): NETGEAR ProSAFE Network Management System getFilterString SQL Injection Remote Code Execution Vulnerability (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-38102 and fix it if it is affected.

What it is: CVE-2023-38102 is a high-severity missing authorization vulnerability in NETGEAR ProSAFE Network Management System, published on 3 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-38102 in the wild and no public exploit code.

Affected product: NETGEAR ProSAFE Network Management System. 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-2023-38102/ (Markdown: https://insights.sbomify.com/CVE-2023-38102/index.md)
```

## Sources

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

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