dbcve.org
Prosafe Network Management SystemApplication · Netgear

CVE-2023-44450

HIGH · 8.8 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 1.7.0.31 or later.
See remediation →
94/100
Remediation priority · Urgent
High EPSS Remotely reachable Zero-click

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 getNodesByTopologyMapSearch SQL Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of NETGEAR ProSAFE Network Management System. Authentication is required to exploit this vulnerability. The specific flaw exists within the getNodesByTopologyMapSearch function. The issue results from the lack of proper validation of a user-supplied string before using it to construct SQL queries. An attacker can leverage this vulnerability to execute code in the context of SYSTEM. Was ZDI-CAN-21858.

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

SQL injection vulnerability in the getNodesByTopologyMapSearch function of NETGEAR ProSAFE Network Management System allows authenticated attackers to inject malicious SQL queries. This can be chained to achieve remote code execution in the context of SYSTEM privileges.

MitigationApply vendor-provided patch immediately. If no patch available, restrict network access to the NMS management interface to trusted IP addresses and implement WAF rules detecting SQL injection patterns as compensating controls.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Confirm Netgear ProSAFE NMS installation
    Identify if Netgear ProSAFE Network Management System is installed on the system by checking installed programs, services, or the NMS installation directory
    Affected if Netgear ProSAFE NMS is not installed on the target system
  2. Check installed NMS version
    Access the NMS web management interface and navigate to the About or Help section to view the version number, or inspect version files in the installation directory
    Affected if Installed version is below 1.7.0.31
  3. Verify getNodesByTopologyMapSearch function exists
    Examine the NMS application binaries or web application files for the presence of the getNodesByTopologyMapSearch function or API endpoint
    Affected if The function is present in the NMS installation
  4. Confirm network accessibility of NMS interface
    Review firewall rules and network configuration to determine if the NMS management interface is accessible from network segments outside of trusted administration networks
    Affected if NMS management interface is exposed to untrusted networks

System is affected if Netgear ProSAFE NMS is installed with a version lower than 1.7.0.31 and the getNodesByTopologyMapSearch component is present, regardless of authentication requirement for exploitation.

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 vendor-provided patch immediately. If no patch available, restrict network access to the NMS management interface to trusted IP addresses and implement WAF rules detecting SQL injection patterns as compensating controls.

Recommended fix High confidence

1.7.0.31

  1. 1. Download the latest ProSAFE Network Management System version 1.7.0.31 from the official NETGEAR support website (kb.netgear.com)
  2. 2. Back up the current configuration and database of the existing installation
  3. 3. Stop the NETGEAR ProSAFE NMS service
  4. 4. Install version 1.7.0.31 using the installer
  5. 5. Restore the configuration backup if needed
  6. 6. Restart the NETGEAR ProSAFE NMS service
  7. 7. Verify the application is running correctly and the getNodesByTopologyMapSearch function is accessible

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

Fix this in Prosafe Network Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-44450 — 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-44450 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