CVE-2019-20676
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 FS728TLP before 1.0.1.26, GS105Ev2 before 1.6.0.4, GS105PE before 1.6.0.4, GS108Ev3 before 2.06.08, GS108PEv3 before 2.06.08, GS110EMX before 1.0.1.4, GS116Ev2 before 2.6.0.35, GS408EPP before 1.0.0.15, GS724TPv2 before 1.1.1.29, GS808E before 1.7.0.7, GS810EMX before 1.7.1.1, GS908E before 1.7.0.3, GSS108E before 1.6.0.4, GSS108EPP before 1.0.0.15, GSS116E before 1.6.0.9, JGS516PE before 2.6.0.35, JGS524Ev2 before 2.6.0.35, JGS524PE before 2.6.0.35, XS512EM before 1.0.1.1, XS708Ev2 before 1.6.0.23, XS716E before 1.6.0.23, and XS724EM before 1.0.1.1.
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 confidenceMultiple NETGEAR network switch devices contain a broken access control vulnerability where certain functions lack proper authorization checks. An authenticated user (or potentially an unauthenticated attacker in some configurations) can access administrative functions without appropriate privileges due to missing function-level access control.
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.0.1.26< 1.6.0.4< 1.6.0.4< 2.06.08< 2.06.08< 1.0.1.4< 2.6.0.35< 1.0.0.15CVSS 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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 device model and firmware versionAccess the switch web management interface and navigate to the Administration or System section to view the current firmware version. Alternatively, check the NETGEAR firmware download page for your specific model.Affected if The installed firmware version falls below the patched versions: Fs728tlp < 1.0.1.26, Gs105e < 1.6.0.4, Gs105pe < 1.6.0.4, Gs108e < 2.06.08, Gs108pe < 2.06.08, Gs110emx < 1.0.1.4, Gs116e < 2.6.0.35, Gs408epp < 1.0.0.15
-
Verify web management interface accessibilityAttempt to access the switch web interface via its IP address on HTTP/HTTPS ports (typically 80/443). Confirm whether the interface responds to local network requests.Affected if The web management interface is accessible from network segments where untrusted users operate
-
Check for unauthorized administrative accountsLog into the switch web interface and navigate to the User Accounts or Administration > User Management section. Review the list of configured accounts and their privilege levels.Affected if Unexpected or unauthorized accounts with administrative privileges exist in the device configuration
-
Review access logs for privilege escalation attemptsIf the switch supports logging, examine system logs or access logs for failed authorization attempts, unusual administrative actions, or requests to undocumented API endpoints.Affected if Logs show administrative functions accessed by accounts lacking appropriate privileges
-
Confirm management VLAN and access restrictionsAccess the switch network configuration and verify which VLANs can reach the management interface. Check if management is restricted to a dedicated VLAN or specific IP ranges.Affected if Management interface is reachable from default VLAN or untrusted network segments
Your environment is affected if you are running any of the listed NETGEAR switch models with firmware versions below the patched thresholds and the web management interface is 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 data1.0.0.151.0.1.41.0.1.26
Update affected NETGEAR switch firmware to versions at or above the specified patched versions (e.g., FS728TLP to 1.0.1.26, GS108Ev3 to 2.06.08, GS116Ev2 to 2.6.0.35, etc.). If patching is not immediately possible, restrict network access to management interfaces and monitor for unauthorized administrative actions.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20676 — 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-2019-20676 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