dbcve.org
Prosafe Network Management SystemApplication · Netgear

CVE-2024-5245

HIGH · 7.8 CVSS v3.1 Published 2024-05-23
Fix available
A fix is available. Upgrade to 1.7.0.37 or later.
See remediation →
80/100
Remediation priority · High
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 Default Credentials Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of NETGEAR ProSAFE Network Management System. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the product installer. The issue results from the use of default MySQL credentials. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of SYSTEM. Was ZDI-CAN-22755.

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

The NETGEAR ProSAFE Network Management System installer uses hardcoded default MySQL credentials. An attacker who has achieved low-privileged code execution on the target system can authenticate to the MySQL database using these default credentials and leverage this to escalate privileges to SYSTEM level and execute arbitrary code.

MitigationChange the default MySQL credentials to strong, unique passwords and update any application connection strings accordingly.

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.37

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

CVSS:3.1/AV:L/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. Verify Netgear ProSAFE NMS installation
    Search for the Netgear ProSAFE Network Management System in installed programs or common installation directories (e.g., C:\Program Files\Netgear, C:\Program Files (x86)\Netgear). Check registry keys under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Netgear' or 'Prosafe'.
    Affected if The software is found installed on the system
  2. Determine installed version
    Locate the version information from the installation directory, registry, or application executable properties. Compare the found version against the affected range: versions prior to 1.7.0.37 are vulnerable.
    Affected if Installed version is lower than 1.7.0.37 (e.g., 1.6.x, 1.5.x, etc.)
  3. Confirm MySQL service is running
    Check if the MySQL service associated with Netgear NMS is running. On Windows, run 'services.msc' and look for MySQL service, or use command 'sc query MySQL' or 'net start' to list running services.
    Affected if MySQL service is running and accessible to the local system
  4. Test for default database credentials
    Locate MySQL configuration files in the Netgear NMS installation directory (commonly in conf, config, or similar subdirectories). Check for embedded credentials in connection strings, configuration XML files, or property files. Attempt to connect to the MySQL database using common default credentials if credentials are discovered.
    Affected if Default or hardcoded MySQL credentials are found in configuration files and database connection succeeds with those credentials

The system is affected if Netgear ProSAFE NMS version lower than 1.7.0.37 is installed with the MySQL service running and accessible using hardcoded default credentials found in configuration files.

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.37 or later
Fixed in 1.7.0.37
Interim mitigation

Change the default MySQL credentials to strong, unique passwords and update any application connection strings accordingly.

Recommended fix High confidence

1.7.0.37 or later

  1. 1. Back up the current ProSAFE Network Management System configuration and any important data.
  2. 2. Download the latest version of NETGEAR ProSAFE Network Management System from the official NETGEAR support website (kb.netgear.com).
  3. 3. Verify the downloaded installer matches version 1.7.0.37 or later.
  4. 4. Stop the ProSAFE NMS service if it is currently running.
  5. 5. Run the installer with administrative privileges.
  6. 6. Follow the on-screen installation wizard prompts to complete the upgrade.
  7. 7. After installation, verify the new version is running (1.7.0.37 or later).
  8. 8. Start the ProSAFE NMS service and confirm all services are functioning correctly.
Caveat Review NETGEAR release notes for any configuration or feature changes between your current version and 1.7.0.37

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
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
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,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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