CVE-2020-35227
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 · uneditedA buffer overflow vulnerability in the access control section on NETGEAR JGS516PE/GS116Ev2 v2.6.0.43 devices (in the administration web panel) allows an attacker to inject IP addresses into the whitelist via the checkedList parameter to the delete command.
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 · moderate confidenceBuffer overflow in the access control whitelist function of NETGEAR JGS516PE/GS116Ev2 switches (firmware v2.6.0.43) allows remote authenticated attackers to inject arbitrary IP addresses into the whitelist via a crafted checkedList parameter sent to the delete command in the administration web panel.
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.43= 2.6.0.43CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Identify the switch modelLog into the device web interface or check the physical device label to confirm the model is either NETGEAR JGS516PE or NETGEAR GS116Ev2Affected if The device model is JGS516PE or GS116Ev2
-
Check the installed firmware versionAccess the administration web panel, navigate to the System or Maintenance section, and locate the firmware version information. Alternatively, use the command line interface or SNMP to query the device firmware versionAffected if The firmware version is exactly 2.6.0.43
-
Verify web administration interface accessibilityDetermine if the HTTP/HTTPS management interface is reachable from network segments outside your trusted management VLAN. Attempt to access the login page from an untrusted network or use network scanning tools to confirm interface exposureAffected if The administration web panel is accessible from untrusted networks (not just from management VLAN)
-
Inspect access control whitelist configurationIn the web administration panel, navigate to the Access Control or ACL settings section. Review the whitelist entries to identify any unexpected or unauthorized IP addresses that were not added by legitimate administratorsAffected if The whitelist contains IP addresses that were not intentionally configured by your admin team
Your environment is affected if you are running firmware version 2.6.0.43 on a JGS516PE or GS116Ev2 switch with the web administration interface accessible to the attacker.
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 dataApply vendor firmware patch when available; otherwise restrict administrative web interface access to trusted management networks/IPs using firewall rules or VLAN segmentation to limit exposure.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-35227 — 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-35227 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