dbcve.org
Prosafe Network Management SystemApplication · Netgear

CVE-2023-41182

HIGH · 8.8 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 1.7.0.20 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 ZipUtils Directory Traversal Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of NETGEAR ProSAFE Network Management System. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed. The specific flaw exists within the ZipUtils 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-19716.

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 ZipUtils class due to insufficient validation of user-supplied paths before file operations. An attacker with valid authentication (which can be bypassed) can traverse the filesystem and write arbitrary files, achieving code execution with SYSTEM privileges.

MitigationApply the vendor-supplied patch from NETGEAR. If unavailable, restrict network access to the management interface and consider disabling the ZipUtils functionality until a fix is available.

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

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 is installed
    Locate the Netgear Prosafe Network Management System installation on the host - typically found in program directories or as a Windows service named similarly to 'NMS' or 'Network Management'
    Affected if The product is not present on the system, then this CVE does not apply
  2. Identify the installed version
    Access the web management interface and look for the version information, typically found in the Help, About, or System Info page. Alternatively, check the installation directory for version files or examine the Windows service details
    Affected if The installed version is any version prior to 1.7.0.20 (e.g., 1.7.0.19, 1.6.x, 1.5.x, etc.) - these versions are vulnerable
  3. Verify the ZipUtils component is accessible
    Confirm the web application is running and accessible - the vulnerability exists in the ZipUtils class which handles zip file operations within the management interface
    Affected if The web management interface is running and responds to requests, the ZipUtils functionality is present and accessible
  4. Check network exposure of the management interface
    Determine if the NMS web interface (typically on ports 8080, 8443, or 80/443) is exposed to the network or accessible from untrusted hosts
    Affected if The management interface is network-accessible beyond trusted administrators, increasing exploitability

If Netgear Prosafe NMS is installed and the version is below 1.7.0.20 with the web interface accessible, the environment is affected by this directory traversal vulnerability.

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.20 or later
Fixed in 1.7.0.20
Interim mitigation

Apply the vendor-supplied patch from NETGEAR. If unavailable, restrict network access to the management interface and consider disabling the ZipUtils functionality until a fix is available.

Recommended fix High confidence

1.7.0.20 or later

  1. 1. Identify the current version of NETGEAR ProSAFE Network Management System by accessing the management interface and checking the 'About' or 'System Info' section
  2. 2. Navigate to the official NETGEAR support page (kb.netgear.com) and locate the download section for ProSAFE Network Management System
  3. 3. Download version 1.7.0.20 or later of the ProSAFE Network Management System software
  4. 4. Follow NETGEAR's official upgrade documentation to apply the update, typically involving stopping the NMS service, running the installer, and restarting the service
  5. 5. Verify the installation was successful by confirming the new version number in the management interface

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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