dbcve.org
Prosafe Network Management SystemApplication · Netgear

CVE-2024-5505

HIGH · 8.8 CVSS v3.1 Published 2024-06-06
Fix available
A fix is available. Upgrade to 1.7.0.37 or later.
See remediation →
94/100
Remediation priority · Urgent
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 UpLoadServlet Directory Traversal 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 UpLoadServlet class. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to execute code in the context of SYSTEM. Was ZDI-CAN-22724.

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

NETGEAR ProSAFE NMS contains a directory traversal vulnerability in the UpLoadServlet class. The lack of proper validation of user-supplied path parameters allows authenticated attackers to manipulate file paths and write arbitrary files, leading to remote code execution as SYSTEM.

MitigationApply vendor-provided patch when available; until then, restrict network access to the NMS management interface to trusted users only and implement additional input validation on file upload endpoints.

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
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. Identify if NETGEAR ProSAFE NMS is installed
    Check for the presence of NETGEAR ProSAFE Network Management System on the host by looking for the NMS installation directory or service
    Affected if The product is not installed on the system
  2. Determine the installed NMS version
    Locate and read the version information file or check the NMS service properties to identify the exact version number installed
    Affected if The installed version is lower than 1.7.0.37
  3. Verify if the UpLoadServlet is accessible
    Attempt to access the UpLoadServlet endpoint (typically via HTTP/HTTPS to the NMS web interface) or check if the servlet is exposed in the web configuration
    Affected if The UpLoadServlet is reachable without additional security controls
  4. Confirm authentication status for the management interface
    Check whether the NMS web management interface requires authentication and whether the UpLoadServlet enforces authentication checks
    Affected if The UpLoadServlet can be accessed with valid credentials or if default/admin credentials are in use

The environment is affected if NETGEAR ProSAFE NMS is installed with a version lower than 1.7.0.37 and the UpLoadServlet is accessible to authenticated users, allowing path manipulation for arbitrary file writes.

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

Apply vendor-provided patch when available; until then, restrict network access to the NMS management interface to trusted users only and implement additional input validation on file upload endpoints.

Recommended fix Moderate confidence

1.7.0.37 or later

  1. Obtain ProSAFE Network Management System version 1.7.0.37 or later from NETGEAR's official support website
  2. Follow NETGEAR's standard upgrade procedure for ProSAFE NMS (typically involves stopping the service, replacing application files, and restarting)
  3. After upgrade, verify the UpLoadServlet is updated and no longer accepts unsanitized paths
  4. Confirm the service runs under the expected account and test that authenticated file operations are properly validated

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
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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