CVE-2024-5247
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 · uneditedNETGEAR ProSAFE Network Management System UpLoadServlet Unrestricted File Upload 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 user-supplied data, which can allow the upload of arbitrary files. An attacker can leverage this vulnerability to execute code in the context of SYSTEM. Was ZDI-CAN-22923.
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 confidenceThe UpLoadServlet class in NETGEAR ProSAFE Network Management System lacks proper validation of user-supplied data during file uploads, allowing authenticated remote attackers to upload arbitrary files. This unrestricted file upload enables remote code execution in SYSTEM context.
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< 1.7.0.37CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Netgear ProSAFE NMS is installedIdentify if the NMS software is running on the network by accessing the management interface (typically HTTPS on port 443 or 8443). Check for the Netgear NMS login page in the browser.Affected if The NMS web interface is accessible on the network
-
Check the installed NMS versionLog into the NMS admin interface and navigate to Help > About, or check the login page footer for the version number. Alternatively, inspect the application's config files or registry for the version string.Affected if The displayed version is below 1.7.0.37
-
Verify file upload servlet accessibilityAttempt to access the upload endpoint directly. The UpLoadServlet is typically found at /upload or /UploadServlet paths under the NMS web application context. Use curl or a browser to request this endpoint.Affected if The servlet responds (even with an authentication redirect) and accepts file upload requests
-
Check if default or weak authentication is in useReview the NMS user accounts configuration. Determine if default credentials are still active or if guest/anonymous access is enabled that could allow unauthenticated upload attempts.Affected if Default credentials are unchanged, or guest access permits reaching the upload functionality
A user is affected if Netgear ProSAFE NMS is running with a version below 1.7.0.37 and the upload servlet is accessible, even with valid authentication.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.7.0.37
Restrict network access to the NMS management interface, apply vendor patches when released, and consider disabling file upload functionality until patched.
1.7.0.37
- Backup the current NetGEAR ProSAFE NMS configuration and database
- Download ProSAFE Network Management System version 1.7.0.37 or later from the official NETGEAR support website (kb.netgear.com)
- Stop the ProSAFE NMS service
- Install the updated version 1.7.0.37 following the vendor's upgrade instructions
- Start the ProSAFE NMS service after installation completes
- Verify the version is showing as 1.7.0.37 or later in the management console
- Test that file upload functionality works correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2024-5247 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-5247 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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