CVE-2019-20699
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 a buffer overflow by an unauthenticated attacker. This affects GS105Ev2 before 1.6.0.4, GS105PE before 1.6.0.4, GS408EPP before 1.0.0.15, GS808E before 1.7.0.7, GS908E before 1.7.0.3, GSS108E before 1.6.0.4, and GSS108EPP before 1.0.0.15.
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 confidenceA buffer overflow vulnerability exists in multiple NETGEAR switch models (GS105Ev2, GS105PE, GS408EPP, GS808E, GS908E, GSS108E, GSS108EPP) that allows unauthenticated attackers to execute arbitrary code or cause a denial of service via specially crafted network requests.
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.6.0.4< 1.6.0.4< 1.0.0.15< 1.7.0.7< 1.7.0.3< 1.6.0.4< 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 NETGEAR switch modelLocate the device label on the physical switch or access the web management interface to view the device model name (GS105Ev2, GS105PE, GS408EPP, GS808E, GS908E, GSS108E, or GSS108EPP)Affected if model is one of the seven affected models listed in the CVE
-
Access the device firmware versionLog into the switch web interface and navigate to System > System Information or Administration > Firmware Upgrade to view the currently installed firmware versionAffected if firmware version cannot be retrieved or displayed
-
Compare firmware version against affected rangesCheck the installed firmware version against these thresholds: GS105Ev2/GS105PE/GSS108E < 1.6.0.4, GS408EPP/GSS108EPP < 1.0.0.15, GS808E < 1.7.0.7, GS908E < 1.7.0.3Affected if installed firmware version is lower than the version threshold for your specific model
-
Verify network accessibility of the deviceConfirm the switch is reachable on the network (ping or port scan) since the vulnerability is exploitable via specially crafted network requestsAffected if device is network-accessible and firmware version is below the affected threshold
You are affected if your switch model is one of the seven listed and the installed firmware version is below the specific threshold for that model.
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.0.0.151.6.0.41.7.0.3
Apply the vendor-supplied firmware updates: GS105Ev2/GS105PE/GSS108E to version 1.6.0.4, GS408EPP/GSS108EPP to version 1.0.0.15, GS808E to version 1.7.0.7, and GS908E to version 1.7.0.3.
Firmware 1.6.0.4 (or later) for GS105E/GS105PE/GSS108E; 1.0.0.15 (or later) for GS408EPP/GSS108EPP; 1.7.0.7 (or later) for GS808E; 1.7.0.3 (or later) for GS908E
- Identify the exact NETGEAR switch model (e.g., GS105E, GS105PE, GS408EPP, GS808E, GS908E, GSS108E, GSS108EPP).
- Visit the NETGEAR support site (https://kb.netgear.com) and locate the firmware download page for your model.
- Download the latest firmware version that resolves the vulnerability: version 1.6.0.4 or later for GS105E, GS105PE, GSS108E; version 1.0.0.15 or later for GS408EPP, GSS108EPP; version 1.7.0.7 or later for GS808E; version 1.7.0.3 or later for GS908E.
- Log into the switch’s web management interface using an administrator account.
- Navigate to the firmware upgrade section (usually under Administration > Firmware Upgrade).
- Upload the downloaded firmware file and initiate the upgrade. Wait for the device to reboot automatically.
- After reboot, verify that the firmware version displayed in the web UI matches the target version to confirm the patch is applied.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20699 — 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-20699 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