dbcve.org
Prosafe Network Management SystemApplication · Netgear

CVE-2023-50231

CRITICAL · 9.6 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 1.7.0.31 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
NETGEAR ProSAFE Network Management System saveNodeLabel Cross-Site Scripting Privilege Escalation Vulnerability. This vulnerability allows remote attackers to escalate privileges on affected installations of NETGEAR ProSAFE Network Management System. Minimal user interaction is required to exploit this vulnerability. The specific flaw exists within the saveNodeLabel method. The issue results from the lack of proper validation of user-supplied data, which can lead to the injection of an arbitrary script. An attacker can leverage this vulnerability to escalate privileges to resources normally protected from the user. Was ZDI-CAN-21838.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A stored Cross-Site Scripting (XSS) vulnerability exists in the saveNodeLabel method of NETGEAR ProSAFE Network Management System. The method lacks proper input validation, allowing attackers to inject arbitrary JavaScript into node labels. Since this XSS can be leveraged to escalate privileges to resources normally protected from the user, it enables a low-privilege user to gain higher-level access.

MitigationApply the vendor patch or firmware update from NETGEAR for this vulnerability. If no patch is available, restrict network access to the management interface and implement Web Application Firewall (WAF) rules to detect and block XSS payloads in the saveNodeLabel endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Prosafe Network Management SystemApplication
Affected:< 1.7.0.31

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed NETGEAR ProSAFE NMS version
    Access the web management interface and navigate to the About or System Information page, or check the software/firmware version displayed in the login footer or admin dashboard
    Affected if The displayed version is any version prior to 1.7.0.31 (e.g., 1.7.0.30, 1.6.x, earlier releases)
  2. Verify web interface accessibility
    Confirm the NETGEAR ProSAFE Network Management System web interface is reachable on the network (typically ports 80/443 or configured HTTP/HTTPS port)
    Affected if The web interface is exposed and accessible, indicating the saveNodeLabel endpoint exists and could be reached
  3. Confirm saveNodeLabel functionality exists
    Locate the node or device management section of the web interface where node labels can be created or edited, as this is where the vulnerable saveNodeLabel method is invoked
    Affected if The node labeling feature is present and available to users, meaning the vulnerable method is in use

You are affected if your installed NETGEAR ProSAFE NMS version is below 1.7.0.31 and the web-based node labeling feature (saveNodeLabel method) is accessible to users in your environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.7.0.31 or later
Fixed in 1.7.0.31
Interim mitigation

Apply the vendor patch or firmware update from NETGEAR for this vulnerability. If no patch is available, restrict network access to the management interface and implement Web Application Firewall (WAF) rules to detect and block XSS payloads in the saveNodeLabel endpoint.

Recommended fix High confidence

1.7.0.31

  1. Download NETGEAR ProSAFE Network Management System version 1.7.0.31 or later from the official NETGEAR support website
  2. Review the release notes and upgrade documentation for any migration requirements
  3. Create a complete backup of the current NMS configuration and database
  4. Stop the NMS services before applying the upgrade
  5. Install version 1.7.0.31 using NETGEAR's standard upgrade procedures
  6. Restart the NMS services after installation
  7. Verify that the saveNodeLabel function no longer accepts unsanitized input and that the XSS vulnerability is remediated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Prosafe Network Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-50231 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-50231 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data