# CVE-2023-38096: NETGEAR ProSAFE Network Management System MyHandlerInterceptor Authentication Bypass Vulnerability

> Remote attackers can bypass authentication in NETGEAR ProSAFE Network Management System due to improper implementation in MyHandlerInterceptor.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 3 May 2024
- **Updated:** 18 Sep 2024
- **Also known as:** GHSA-whh9-qwjx-x7jq

## What is CVE-2023-38096?

CVE-2023-38096 is a critical authentication bypass vulnerability in NETGEAR ProSAFE Network Management System, published on 3 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NETGEAR ProSAFE Network Management System MyHandlerInterceptor Authentication Bypass Vulnerability. This vulnerability allows remote attackers to bypass authentication on affected installations of NETGEAR ProSAFE Network Management System. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the MyHandlerInterceptor class. The issue results from improper implementation of the authentication mechanism. An attacker can leverage this vulnerability to bypass authentication on the system.
. Was ZDI-CAN-19718.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Netgear Prosafe Network Management System.

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

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

## Is CVE-2023-38096 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-38096 exists.

Public exploit code:

- NETGEAR ProSafe Network Management System 300 Arbitrary File Upload (metasploit)

## Other vulnerabilities in NETGEAR ProSAFE Network Management System

- [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)
- [CVE-2024-5505](https://insights.sbomify.com/CVE-2024-5505/): NETGEAR ProSAFE Network Management System UpLoadServlet Directory Traversal Remote Code Execution Vulnerability (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-38096 is a critical authentication bypass vulnerability in NETGEAR ProSAFE Network Management System, published on 3 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-38096 exists.

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-38096/ (Markdown: https://insights.sbomify.com/CVE-2023-38096/index.md)
```

## Sources

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

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