CVE-2020-35783
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 · uneditedCertain NETGEAR devices are affected by lack of access control at the function level. This affects JGS516PE before 2.6.0.48, GS116Ev2 before 2.6.0.48, JGS524Ev2 before 2.6.0.48, and JGS524PE before 2.6.0.48. The NSDP protocol version allows unauthenticated remote attackers to obtain all the switch configuration parameters by sending the corresponding read requests.
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 confidenceThis is a broken access control vulnerability in the NSDP (NETGEAR Switch Discovery Protocol) on affected NETGEAR switches. The NSDP protocol implementation lacks proper function-level authorization checks, allowing any unauthenticated remote attacker to send read requests and obtain all switch configuration parameters, including sensitive settings.
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< 2.6.0.48< 2.6.0.48< 2.6.0.48< 2.6.0.48CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Identify switch modelLog into the switch web interface or use SNMP to query the device sysDescr, or check the physical device label to confirm the exact model numberAffected if Model is JGS516PE, JGS524E, JGS524PE, or GS116E
-
Check installed firmware versionAccess the switch web interface under System > Management > Firmware or use SNMP OID for firmware version, or check via console boot logsAffected if Firmware version is below 2.6.0.48 (for example, 2.6.0.40 or earlier)
-
Confirm NSDP protocol is enabledAccess the switch web interface under Switching > NSDP or similar menu, or query the device configuration to verify if NSDP service is turned onAffected if NSDP is enabled and running on the switch
-
Verify NSDP port accessibilitySend a UDP packet to port 63323 (default NSDP port) toward the switch IP address using netcat or nmap, or capture network traffic to see if the switch responds to NSDP broadcast requestsAffected if The switch responds to unauthenticated NSDP requests on the network
You are affected if you have a JGS516PE, JGS524E, JGS524PE, or GS116E switch running firmware below 2.6.0.48 with NSDP enabled and accessible from your network.
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.
From vendor data2.6.0.48
Update affected NETGEAR switch firmware (JGS516PE, GS116Ev2, JGS524Ev2, JGS524PE) to version 2.6.0.48 or later. If immediate patching is not possible, restrict network access to the NSDP protocol via firewall or VLAN segmentation.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-35783 — 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-2020-35783 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