Gs108ev3 FirmwareOperating system · Netgear

CVE-2020-5641

MEDIUM · 6.5 CVSS v3.1 Published 2020-11-24
Fix available
A fix is available. Upgrade to after 2.06.10 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Cross-site request forgery (CSRF) vulnerability in GS108Ev3 firmware version 2.06.10 and earlier allows remote attackers to hijack the authentication of administrators and the product's settings may be changed without the user's intention or consent via unspecified vectors.

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 confidence

Cross-site request forgery (CSRF) vulnerability in Netgear GS108Ev3 switch firmware version 2.06.10 and earlier allows remote attackers to hijack authenticated administrator sessions by tricking logged-in users into visiting malicious pages, enabling unauthorized modification of device settings.

MitigationApply vendor firmware update when available; in the interim, administrators should avoid browsing untrusted sites while logged into the device management interface and use network segmentation to limit exposure.

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
Gs108ev3 FirmwareOperating system
Affected:<= 2.06.10

CVSS 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
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Locate the physical device or log into the switch management interface and confirm the model number is GS108Ev3
    Affected if The device is a Netgear GS108Ev3 switch
  2. Check the installed firmware version
    In the web management interface, navigate to the Administration or System section to view the firmware version, or use the command-line interface if available
    Affected if The firmware version is 2.06.10 or earlier
  3. Verify remote management is enabled
    Check the switch configuration for remote/web management settings - typically found under Administration > Remote Management or similar
    Affected if Remote management interface is accessible from network segments where users browse untrusted sites
  4. Confirm admin session exposure risk
    Determine if administrators access the device management interface while simultaneously browsing other websites
    Affected if Administrators log into the device interface and browse untrusted sites in the same browser session

You are affected if you have a Netgear GS108Ev3 switch running firmware version 2.06.10 or earlier with the web management interface accessible and administrators who may browse untrusted sites while logged in.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 2.06.10
Interim mitigation

Apply vendor firmware update when available; in the interim, administrators should avoid browsing untrusted sites while logged into the device management interface and use network segmentation to limit exposure.

Fix this in Gs108ev3 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-5641 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-5641 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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